EDIT : I got rid of the problem and managed to root my phone.
I'm having trouble rooting the K3 note flashed with VIBE UI 3.0. I'm using Lenovo K50a40, Indian Version and I flashed the Dev version of Vibe UI ROM (v 3.0 from hackerpower's signature) . The flashing went all fine. Then I tried to reroot the phone but I noticed that the recovery was the stock one. So I proceeded to reflash the recovery using fastboot but it showed that the file had been downloaded but could not be flashed to the recovery partition. I thought of using SP Flash Tool to flash the recovery. I flashed AthlonX's material TWRP recovery and it flashed okay. Then on rebooting the phone I find it remains stuck on the boot logo with Lenovo written on white backdrop. There's also text written in a small black strip on the bottom left which says "=>Tool DL Image Fail" . The phone stays on that screen for a minute or two and then goes out. Earlier I couldn't boot into the phone due to the above mentioned problem. Then I waited for the battery to drain and then powered the phone on normally (without pressing the button combination for recovery mode) and the phone booted up just fine but the recovery was the stock one .
From all this, there's one thing I've concluded- that this phone has some kind of defense mechanism that protects against installing a custom recovery. This occurred even when I tried rooting on Stock 2.5 VIBE UI. That time I overcame the problem by flashing recovery using fastboot and then booting directly into the recovery instead of system. Now, however, fastboot isn't able to flash the recovery (the transfer of the image is successful but the flashing fails) .
Finally, I request anyone who can help me in any way to Root the phone or to get a recovery installed to please reply.
Thanks.
how were you able to root it
Lord AJ said:
EDIT : I got rid of the problem and managed to root my phone.
I'm having trouble rooting the K3 note flashed with VIBE UI 3.0. I'm using Lenovo K50a40, Indian Version and I flashed the Dev version of Vibe UI ROM (v 3.0 from hackerpower's signature) . The flashing went all fine. Then I tried to reroot the phone but I noticed that the recovery was the stock one. So I proceeded to reflash the recovery using fastboot but it showed that the file had been downloaded but could not be flashed to the recovery partition. I thought of using SP Flash Tool to flash the recovery. I flashed AthlonX's material TWRP recovery and it flashed okay. Then on rebooting the phone I find it remains stuck on the boot logo with Lenovo written on white backdrop. There's also text written in a small black strip on the bottom left which says "=>Tool DL Image Fail" . The phone stays on that screen for a minute or two and then goes out. Earlier I couldn't boot into the phone due to the above mentioned problem. Then I waited for the battery to drain and then powered the phone on normally (without pressing the button combination for recovery mode) and the phone booted up just fine but the recovery was the stock one .
From all this, there's one thing I've concluded- that this phone has some kind of defense mechanism that protects against installing a custom recovery. This occurred even when I tried rooting on Stock 2.5 VIBE UI. That time I overcame the problem by flashing recovery using fastboot and then booting directly into the recovery instead of system. Now, however, fastboot isn't able to flash the recovery (the transfer of the image is successful but the flashing fails) .
Finally, I request anyone who can help me in any way to Root the phone or to get a recovery installed to please reply.
Thanks.
Click to expand...
Click to collapse
i have been using the sp flash tool to download the recovery i want and every time goes back to the stock one
obviously i lost my gapps with the update
but i dont have the google play services issue since i had to re install stock rom and never update google services and just when ahead and applied the updates 2.8 and 3.0,
do you have any ideas
daniiaroxyo said:
i have been using the sp flash tool to download the recovery i want and every time goes back to the stock one
obviously i lost my gapps with the update
but i dont have the google play services issue since i had to re install stock rom and never update google services and just when ahead and applied the updates 2.8 and 3.0,
do you have any ideas
Click to expand...
Click to collapse
If the recovery goes back to stock then you should probably try to boot into the recovery before rebooting to system after SP Flash Tool has done it's job.
Hi so I down loaded one more time the recovery thru sp tool
But this time I took the battery out for few seconds instead of rebooting right away
And it worked
Once I rooted back the phone I tried flashing the gapps but it didn't work
I tried changing the permission s thru root explorer for the google base app as I so on a post and nothing
Any ideas
Related
Hello,
Tried rooting my phone with no prior experience. Worked, but eventually I got to where the phone wouldn't boot past splash screen (logo came up, then screen went black while backlight is on and didn't respond to stimuli until battery was removed). Possibly resulted from a build.prop file problem. Did get into boot though, so I fixed that problem by installing a cyanogen rom from a zip file using twrp recovery. I didn't want a custom mod though since I'm used to the look and feel of the 4.0.3 ICS I had, and the cyanogen doesn't seem to have google play so I can't even download anything (original purpose of rooting was to get incompatible apps by spoofing via build.prop file). Currently trying to get back to stock. Unfortunately I didn't make a nandroid backup of the system before the problem occurred, hence I have no backup to flash.
What I tried:
1. Use the official HTC 4.0.3 RUU .exe to upload to the phone. Unfortunately HTC Sync doesn't see this phone, even though I have the correct drivers installed.
2. Attempted to use twrp recovery to install the rom.zip extracted from the RUU directly, the same way I successfully installed the cyanogenmod rom. Failed, claiming it's unable to open zip. The .zip file was checked for integrity and returned by an archiver app.
3. Tried to use these commands from the cmd with phone connected to install the .zip from fastboot:
fastboot erase cache
fastboot oem rebootRuu
fastboot flash zip rom.zip (rom.zip being the functional file of the stock rom)
Failed, saying it's not allowed. Tried it with both locked and unlocked bootloader, no difference.
4. Unzipped the file and tried to flash the system.img file directly, but that failed with a "data length is too large" error.
5. My recovery being twrp 2.1.1, tried looking for altenatives. Can't find any links to download the WCX recovery, but I found several for newer twrp versions, including 2.3.1.0 and 2.6.3.0 which I tried downloading flashing. After flashing the phone got stuck at the cyanogenmod loading logo and wouldn't boot further, and the recovery itself didn't work, just showed the HTC splash, turned black, then booted again normally, getting stuck at the cyanogen logo. Same thing for the 2.6.3.0 version, so I reflashed the original 2.1.1, at which point I can get into recovery but the phone is still stuck at the cyanogenmod during normal boot. At this point I installed the original cyanogenmod .zip from recovery and now at least the phone boots up normally. Still need to get stock back somehow.
Out of ideas and exhausted from this. Any help would be appreciated. Perhaps anyone has a working stock 4.0.3 rom for the Vivid, nandroid backup, etc., or any other ideas. Thanks for reading.
Oh crap...
OK... First... Stock rom can be found in development... Most of the roms there are stock... Read the OP... It'll tell you...
Second... You should use TWRP 2.5.3.0 or something like that I forget...
Third... When you tried the ruu... Did you relock your bootloader...
Side note... Could you get your phone to show up with 'fastboot devices'
Hello everybody,
I rooted my Xperia Z1 about 8 months ago in order to install the 5.1.1 update which didn't roll out for my device probably because it was a global version (5.0.1 was the last OTA). I did a clean install with no problems, flashed DualRecovery, SuperSu, and BusyBox was working just fine. Everything was working perfectly.
About 3 months ago, I tried updating BusyBox, only to tell that the update failed (couldn't install in the path it used to be try changing the path), I read and read, and found that the solution was to delete a certain file from root that prevented me from modifying certain folders and their content(even with root access), and then do a clean install in a different path than the former one. However, I couldn't gain root access to my files, no root explorer worked! It bugged me, but I was busy at that time, so I couldn't resolve it.
Few weeks later I tried rebooting into recovery, but no method worked, no apps, no key combination, no adb, nothing at all worked! After 2 hard days I managed to install TWRP recovery using NUTS recovery project. I rebooted several times, and it was still working. I then installed BusyBox with no problems, and everything was back to perfect. Later I decided to install CM 12.1 because I always used on my Samsung Galaxy Nexus and I always loved it. So using my now working recovery, I backed everything up on a USB and then flashed CM 12.1 WITHOUT its recovery along with a GAPPS package.
CM was installed, which then rebooted into its recovery and tried to install the GAPPS package. The GAPPS installation was a fail. CM recovery asked me to try using TWRP to do such installation ( go figure! ); in fact, CM recovery couldn't flash anything besides another CM 12.1 update. After this point I wasn't able in any possible way to enter TWRP nor install it. Even if I want to flash using fastboot I couln't! adb reads my device just fine, and can use it to reboot into flashmode, which doesn't seem to be functioning properly. The blue light turns on but there isn't a thing on the screen, fastboot can't recognize is it and hence I can't flash anything using fastboot.
Should I reflash partitions if this could be done on Z1? ( I did it before on my Nexus ) Can I use Odin? I even doubt I can enter download mode on my phone
Any help would be much appreciated.
Thanks in advance!
Anyone?
No?
Ok! :sad:
Is your bootloader unlocked? To run cm on our z1 you need an unlocked bootloader because cm needs a custom kernel.
You can try Sony companion app or androxydes flashtool in combination with a pre-rooted ftf to reach stock again.
The thing is even Sony flashtool (Emma) is not reading my phone, it detects a device in the USB port, but not the device!
I managed to install TWRP using TWRP Manager app that I downloaded from APKmirror website. I installed GApps and it is working fine right now.
TWRP Manager said that I should have a FOTA recovery or something like that, and if I don't have one then I am installing the recovery on my responsibility.
Still no bootloader or flash mode. Neither Emma nor Odin are identifying the phone. Although my phone lights blue, but the screen shows nothing!
Mohdhamm said:
The thing is even Sony flashtool (Emma) is not reading my phone, it detects a device in the USB port, but not the device!
Still no bootloader or flash mode. Neither Emma nor Odin are identifying the phone. Although my phone lights blue, but the screen shows nothing!
Click to expand...
Click to collapse
AFAIK, Emma hasn't been updated for a LONG time. It will remain defunct with no updates and no support. Use flashtool from androxyde if you want to continue using Sony's stock ROM.
No bootloader or flash mode detection: That usually means the drivers that interfaces with your phone is missing. Search around XDA for the correct fastboot and adb drivers for your PC's OS.
My approach for fixing your issue: Find the right drivers and put a stable Lollipop ROM on your sdcard. If you have fastboot working (make sure you have unlocked bootloader), flash boot image from the Lollipop zip and flash the recovery image found in some Lollipop threads. If everything goes well, your phone will bootloop, but you'll have working recovery. Press Vol Down when the Sony Logo appears on screen to enter TWRP. Since you saved a backup of your phone elsewhere, erase all the partitions (minus sdcard), format them to ext4, and flash the Lollipop ROM from your sdcard.
let me explain everything why have i created this thread.
My phone was only charging when switched off. I was on Lineage OS (by daniel_hk) at that time so i thought it is because of that custom ROM.
I, then, intended to flash stock ROM, this one: https://forum.xda-developers.com/k3-note/development/official-build-lenovo-k3-note-k50a40-6-t3370537
debloated version.
I booted into TWRP recovery (v3.1.1-2 by daniel_hk).
Wiped everything and tried flashing K3 Note S433 Debloated ROM from the link i mentioned above. I received error 7. Now i was stuck without any OS in the phone.
Then I tried to flash other version of twrp (3.1.1-0) in phone using sp flash tool but received another error- "PMT is changed for the ROM! It must be downloaded" :/
I googled and found the solution is format the flash using sp flash tool. I did it and flashed the recovery but my phone went dead completely! No responses at all.
Finally i decided to install the original S433 ROM in K3 Note using SP Flash tool but then i receved another error - "BROM: Error 4008"
Then I tried another version of SP Flash tool, v5.1628 (previously v5.1604), Received the PMT changed error then formatted again then flashed the Original ROM.
Now my phone is Unbricked but still not charging and i have no IMEI also.
Favours/Helps that i want-
1. Main thing i want my phone to charge when it is powered on. Watched this video on youtube https://www.youtube.com/watch?v=N7qtDMu_WTU but I am not able to enter Engineering Mode.
2. I want to install debloated version of this ROM through TWRP and for that i have to flash twrp now but to flash TWRP i will need to format using SP Flash tool first (becuase of error "PMT is Changed in the ROM") and if i do that my phone will be bricked again! If i somehow flashed the recovery then i'll not be able to flash the debloated version of the ROM because of the "Error 7".
3. Want my IMEI back
Any Help will be really appreciated.
And sorry if any similar thread already exists I couldn't find the best solution for me anywhere so i created my own!
dude , first thing to remember;
even if your os is completely gone and recovery option is still working , then don't ever do these stupid things.
I've been in your place . But i always knows that if your recovery is still working then there's 99.9% you can fix it.but it seems like you've ruined everything with other flash tools. Dude , unlike every phones, k3 note has it's own k3 note manager software available in xda forums. You can download twrp backups here . Lenovo stock rom backup was here, only you have to do is download and place it on the correct folder. Then press restore!!!
But you ruined everything. I don't know if it turn on again. You came here after all of this and asking us to help now? I
install a custom rom after installing the stockrom (which got error7 during install)
after u get error7 when installing the firmware,,you wont have any os for the phone to boot.
just flash someother custom rom after u got that error.. phone will boot up.
Please compare whether all files of the stockrom you downloaded are extracted,i got error 7,and when i investigated the reason was that one of the file inside the rar file was not extracted.which inturn caused error during instalation
aK_mr3'ofive said:
let me explain everything why have i created this thread.
My phone was only charging when switched off. I was on Lineage OS (by daniel_hk) at that time so i thought it is because of that custom ROM.
I, then, intended to flash stock ROM, this one: https://forum.xda-developers.com/k3-note/development/official-build-lenovo-k3-note-k50a40-6-t3370537
debloated version.
I booted into TWRP recovery (v3.1.1-2 by daniel_hk).
Wiped everything and tried flashing K3 Note S433 Debloated ROM from the link i mentioned above. I received error 7. Now i was stuck without any OS in the phone.
Then I tried to flash other version of twrp (3.1.1-0) in phone using sp flash tool but received another error- "PMT is changed for the ROM! It must be downloaded" :/
I googled and found the solution is format the flash using sp flash tool. I did it and flashed the recovery but my phone went dead completely! No responses at all.
Finally i decided to install the original S433 ROM in K3 Note using SP Flash tool but then i receved another error - "BROM: Error 4008"
Then I tried another version of SP Flash tool, v5.1628 (previously v5.1604), Received the PMT changed error then formatted again then flashed the Original ROM.
Now my phone is Unbricked but still not charging and i have no IMEI also.
Favours/Helps that i want-
1. Main thing i want my phone to charge when it is powered on. Watched this video on youtube https://www.youtube.com/watch?v=N7qtDMu_WTU but I am not able to enter Engineering Mode.
2. I want to install debloated version of this ROM through TWRP and for that i have to flash twrp now but to flash TWRP i will need to format using SP Flash tool first (becuase of error "PMT is Changed in the ROM") and if i do that my phone will be bricked again! If i somehow flashed the recovery then i'll not be able to flash the debloated version of the ROM because of the "Error 7".
3. Want my IMEI back
Any Help will be really appreciated.
And sorry if any similar thread already exists I couldn't find the best solution for me anywhere so i created my own!
Click to expand...
Click to collapse
i hv facing same issue try every think bt nothing is work thn i hv flash my phone sp flash with original stock rom and when i flash i untk recovery option bcoz in 89 percent i got error than aftr untk it successfully flash and when i start i only show twrp thn i reconnect my phone to pc and untck all in stock rom only tck recovery and successfully flash recover and restart my mobile....... and boom its work nw i very happy
aK_mr3'ofive said:
let me explain everything why have i created this thread.
My phone was only charging when switched off. I was on Lineage OS (by daniel_hk) at that time so i thought it is because of that custom ROM.
I, then, intended to flash stock ROM, this one: https://forum.xda-developers.com/k3-note/development/official-build-lenovo-k3-note-k50a40-6-t3370537
debloated version.
I booted into TWRP recovery (v3.1.1-2 by daniel_hk).
Wiped everything and tried flashing K3 Note S433 Debloated ROM from the link i mentioned above. I received error 7. Now i was stuck without any OS in the phone.
Then I tried to flash other version of twrp (3.1.1-0) in phone using sp flash tool but received another error- "PMT is changed for the ROM! It must be downloaded" :/
I googled and found the solution is format the flash using sp flash tool. I did it and flashed the recovery but my phone went dead completely! No responses at all.
Finally i decided to install the original S433 ROM in K3 Note using SP Flash tool but then i receved another error - "BROM: Error 4008"
Then I tried another version of SP Flash tool, v5.1628 (previously v5.1604), Received the PMT changed error then formatted again then flashed the Original ROM.
Now my phone is Unbricked but still not charging and i have no IMEI also.
Favours/Helps that i want-
1. Main thing i want my phone to charge when it is powered on. Watched this video on youtube https://www.youtube.com/watch?v=N7qtDMu_WTU but I am not able to enter Engineering Mode.
2. I want to install debloated version of this ROM through TWRP and for that i have to flash twrp now but to flash TWRP i will need to format using SP Flash tool first (becuase of error "PMT is Changed in the ROM") and if i do that my phone will be bricked again! If i somehow flashed the recovery then i'll not be able to flash the debloated version of the ROM because of the "Error 7".
3. Want my IMEI back
Any Help will be really appreciated.
And sorry if any similar thread already exists I couldn't find the best solution for me anywhere so i created my own!
Click to expand...
Click to collapse
hows your phone?? alive??
Hey!I have a serious problem with my phone and I really need some help
My phone was running Android 8.1 (Custom ROM) before someone cracked the screen of my phone.After that i leave the phone to a service for repair.All good since i take it back.After i went to home i do a factory reset and guess what...bootloop.I tried to flash other ROM ( I was using TWRP 3.2) but smae results...I tried to flash other version of TWRP ,but when i typed in adb fastboot boot (recovery image name).iso the phone still remains in FASTBOOT and nothing happened.
Finally I saw that an older version of TWRP was workig (cofface TWRP recovery) and i flashed the original ROM (MIUI) wich was working
Now I want to know what they did to my phone.Why i can't flash any other recovery or Custom ROMs...What can I do?
I really need some help
Hello guys!
Yesterday I tried to flash the newest Lineage-built to my new G7+ (XT1965-3, bought in Germany via Amazon), but something went wrong and now I'm afraid, I bricked my phone.
It's not my first flash of Lineage, as I did this in the past already on some older Phones (SII, SIII, S5), but it's the first time, that I have a major issue.
So I followed all the steps on the Lineage-Wiki (on Win10).
After flashing the recovery (the lineage-recovery, not TWRP) I wasn't able to enter the recovery-mode, so the phone booted to StockRom. And probably this was the problem: As it didn't react to VolumeDown+Power, I reflashed the recovery a second time. After that the touch-screen is not working any more.
I am able to enter the recovery-mode and I can boot to Stock-Rom, but in both modes the phone does not react to touch, so I can only use the Volume- and Power-Buttons.
Probably I made more mistakes after that: I thought, that a factory-reset would help, but It didn't. I also relocked the bootloader, but as I saw, that it also did not bring any solution, I unlocked it a second time.
Conclusion: I have a brand new phone, with lineage-recovery, an unlocked bootloader but without touch working.
I also tried to flash Lineage, but the sideload got stuck at 47%. So Lineage is not installed and it boots into Stock, where I can not get any further without touch.
Has anyone any idea, what could be the issue and how I can fix it? I would like to start from scratch, but I don't know, what is the exact problem and if i can for example return to stock recovery.
Thank you!
---- EDIT ----
If it helps: I am able to boot TWRP via "fastboot boot twrp-xxx.img". And in TWRP the touch works!
I could flash lineage directly via TWRP from external sd-card, but i am afraid that after that I won't be able to return if something goes wron.
probably your best bet is to go right back to stock using the LMSA tool and starting fresh. I've seen others encounter similar issues on different devices and always the cleaneast solution was just to role back everything and start over.
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
joglxv said:
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
Click to expand...
Click to collapse
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
digitaljeff said:
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
Click to expand...
Click to collapse
I'm having a similar problem. At first touch was fubar but I was able to return to stock using LMSA and now touch works. I can load TWRP with fastboot and even install a custom ROM and TWRP, but installing any custom ROM results in a boot loop during the finding and installing updates part of the phone setup during first boot. I'm tried Evolution X which I was running previously(for about a month, and then a boot loop started yesterday), PixelOS 10, and AncientOS, but all result in the boot loop on first boot after connecting to wifi.
Fixed
I fixed this somehow by manually flashing the latest stock firmware to slot a, and then extracting the evolution x Rom and manually extracting the IMG files inside and manually fastboot flashing those to slot b. I then set b as the active slot and booted up, patched the boot image with magisk, flashed that, and everything works. Not sure why twrp wouldn't do the trick.
Finally had the time to install Lineage. Now everything works.
I followed the instructions someone posted in the [ROM][OFFICIAL] LineageOS 17.1 [nightlies]-thread and the instructions of the lineage-wiki:
1. fastboot boot TWRP
2. sideload the copy-partitions.zip from lineage-wiki
3. factory reset via TWRP (wipe cache, dalvik and data)
4. sideload lineage
5. reboot bootloader
6. fastboot boot TWRP
7. sideload magisk
8. reboot system
Had a little bootloop the first time rebooting the system, but that was because I forgot to wipe data-partition in step 3. Wiping data and rebooting did it for me.
So I have a working Lineage17.1 with root via Magisk.
Thank you for the help!
I had exactly the same problem like you had. Bought a brand new moto g7 plus and after recovery flash, Touchscreen was not working anymore. I could manage to go back to the bootloader, sideloaded TWRP, but side loading lineage worked for me then. It seemed to be stuck on 47 percent, but this seems to be a normal issue, the file was there and after installing, touchscreen worked normally.