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??
Related
First of all sorry for my English...
Yesterday I was trying to install vanir room to my p880 after 10 hours I rooted the phone and unlock the bootloader then installed cwm but after reboot I get stuck on logo so I used kdz and load LGP880AT-00-V20a-262-000-MAR-26-2013+0 with (after 4 hours ) then i try using twrp and finally load the room (vanir_p880_4.4.4.112414.zip) and Gapps after rebooting I started getting crashes ( aosp keyboard, com.google, home and back buttons etc didn't work)
so again kdz then i try other room Paranoid but the same thing..
What I'm doing wrong? I used factory reset, wipe etc but same results
what gapps you flashed?
blansh heretics
The ones that are here http://forum.xda-developers.com/showthread.php?t=2439739
But I load another rom without gapps and got same errors, wizard stopped, com.Google stopped. And keyboard.
G0ll0 said:
The ones that are here http://forum.xda-developers.com/showthread.php?t=2439739
But I load another rom without gapps and got same errors, wizard stopped, com.Google stopped. And keyboard.
Click to expand...
Click to collapse
I don't really know what happened, did you successfully flashed kdz?
Where did you get it from? Here?: http://lg-phone-firmware.com/index.php?id_mod=15
Try to flash one of these (choose correct one for you)
Than you have to install recovery again.
But before that you can try to wipe /system, /data, /cache and then flash CM11 (I know it works without problems)
And I recommend you these Gapps: http://forum.xda-developers.com/showthread.php?t=2397942
LGaljo said:
I don't really know what happened, did you successfully flashed kdz?
Where did you get it from? Here?: http://lg-phone-firmware.com/index.php?id_mod=15
Try to flash one of these (choose correct one for you)
Than you have to install recovery again.
But before that you can try to wipe /system, /data, /cache and then flash CM11 (I know it works without problems)
And I recommend you these Gapps: http://forum.xda-developers.com/showthread.php?t=2397942
Click to expand...
Click to collapse
well... yes i think I flashed kdz (LGFlashTool ?) I used kdz to recover my phone to original, I know my phone is Korean version and right now I use P88020A-EUR-XXX original firmware installed with kdz
What is CM11? and how i flash it?
so I have to root and unlock bootloader again and use twrp again right?
G0ll0 said:
well... yes i think I flashed kdz (LGFlashTool ?) I used kdz to recover my phone to original, I know my phone is Korean version and right now I use P88020A-EUR-XXX original firmware installed with kdz
What is CM11? and how i flash it?
so I have to root and unlock bootloader again and use twrp again right?
Click to expand...
Click to collapse
I think you should try with CWM first, get it: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.5-p880.img
you can flash it with this app if you are rooted: https://play.google.com/store/apps/details?id=com.cgollner.flashify
then you can download CM11 from here: http://download.cyanogenmod.org/?device=p880
and gapps from last mine post
and then boot to recovery, do factory reset and wipe /system, then flash rom and gapps.
Hope it helps
Crash After Flash OTA Vanir 5.0
I had a similar experience. I was installing OTA latest update of Vanir...not realising that it was 5.0...a screen came up telling me that it needed to flash another recovery...not realising why it needed that, I ignored the request to flash. Of course, I then "bricked" the phone. I was able to install the original JB 4.12 (v20c) back onto the phone but now it won't root. I've tried almost every method in this forum to no avail.:
ADB just gives a message "error: closing" when I use the boot.exe method
o4xr method does nothing
all-in-one method also does nothing
ADB does recognise the device. Drivers are installed. Any help is welcome!
BermiePT said:
I had a similar experience. I was installing OTA latest update of Vanir...not realising that it was 5.0...a screen came up telling me that it needed to flash another recovery...not realising why it needed that, I ignored the request to flash. Of course, I then "bricked" the phone. I was able to install the original JB 4.12 (v20c) back onto the phone but now it won't root. I've tried almost every method in this forum to no avail.:
ADB just gives a message "error: closing" when I use the boot.exe method
o4xr method does nothing
all-in-one method also does nothing
ADB does recognise the device. Drivers are installed. Any help is welcome!
Click to expand...
Click to collapse
Have you tried to flash a recovery using fastboot? You won't need to root (if you are going to use a custom ROM) and/or it will be easier with a custom recovery
Soft brick after last update.
Hello,
I seem to have a similar problem. I updated a few days ago using Vanir updater. There were no warnings re updating the recovery, just a warning regarding losing root. I checked restore root. The phone rebooted to the bootloader logo, then to a black screen. Now, I can access Cyanogen recovery, SW update mode, abd fastboot mode using buttons and the recovery options. ADB can see the phone only in recovery mode, but not in fastboot or SW update mode. CM recovery has no option to mount USB storage, so my PC cannot see the phone, and I cannot side load a new recovery and flash a new ROM.
Is there any way to use ADB if it cannot see your phone in fastboot or SW mode? Perhaps modify the settings.secure string to enable ADB? ADB can see the phone in recovery mode.
Otherwise I will try flashing a stock ROM via KDZ or LG firmware update tool, the re-root and proceed - but rooting was a major ordeal the first time, so I would like to avoid doing that again.
Thanks in advance.
I really hope I have not bricked my mi3.
I recently installed cyanogen 12 Dev rom onto the phone but had terrible trouble installing a gapps package.
I was using cwm recovery r11, so I decided to change the recovery to twrp.
Still I could not get gapps to install! So earlier on I noticed the phone was really hot and over heating and when I looked at it it was stuck on the cyanogen boot logo.
I don't know how this happened but anyway I put the phone into recovery to try and cool it.
I then backed up the current rom on twrp and then tried to install a previous aosp rom that was working fine with gapps..
But when I wiped cache and then tried to install the zip file was missing so I tried to restore the backed up cyanogen 12 rom but the restore was not there.???
So twrp was telling me their was no os on the phone.
I tried to turn off the phone and then reboot to recovery in the hope the restore would be there but now the phone won't do anything.. Nothing.!
Even when I charge it no lights, nothing..
Am I f###ked or is their hope.
Please help.
?????
Try to flash MIUI stock rom with fastboot mode via mi flash tool...
You can find the full guide here http://forum.xda-developers.com/xiaomi-mi-3/help/fix-bricked-xiaomi-mi3-mi4-t3154558
This is the latest fastboot rom
Press the volume down key and power key...you should see the fastboot menu(just an fastboot image) then use miflash
For more info check this links http://en.miui.com/thread-28640-1-1.html
http://en.miui.com/thread-44950-1-1.html
http://enbigota.d.miui.com/V6.5.1.0...es_V6.5.1.0.KXDMICD_4.4_global_6761411d29.tgz
Thanks lads , got it sorted thank God .
Sent from my A0001 using Tapatalk
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
Hello community,
I assume, I got a big problem. First of all, my z3c is stucked in away that i cant do anything right now.
I unlocked the bootloader some time ago and tried to flash cm on my phone. It didnt worked out for me and because i hadnt time, I was flashing via flashtool the concept android.
Yesterday I thought to try it once more. I was downloading the newest twrp for z3c and tried to flash cm from sd card and internal storage. Before I flashed, wiped th chache and personal etc.. But it says always there is a error 7, so I deleted the assets line in the update-script. Now if I want to flash cm or any other rom with the same change, it says that it couldnt find the binary-uptade (but actualy it is in the same folder). Afterwards I thought maybe it is because of the twrp and I wanted to change to the cm recovery via flashtool. I recognized that is impossible for me, because flashtool doesnt recognized my phone anymore. Win 7 says te driver is installed correctly, but shows the device as unknown! So I am stucked with twrp on my phone and cant flash via flashtool or twrp any rom.
Anyone got some help which I can do? Anything to get working rom on my phone for daily use? Thanks a lot in advance for your answer. And I am sorry if this problem was already posted.
Bests, Philipp
Hi. I had miui7 running on my Mi3 and I wanted to run cm13. I used cm12 before but went back to stock miui7.
But I needed to update baseband to update to cm13 so i used the cm13update.zip from jrizzoli.github.io/dotfiles/ and it had TWRP (modified maybe?) as the recovery and I easily installed CM13 after that. Later I updated via OTA several times and it went fine until the last time when it would not boot anymore and would stay stuck in bootloop or if i went to recovery, it would start installing the last cm13 update and then end with error 7 and would give system partition has unexpected contents error.
I tried to do EVERYTHING I could to make the phone show ANYTHING other than the cm13 updating in recovery screen or the ANNOYING cm13 logo. NOTHING worked.
I tried using miflash to flash old kitkat 4.3 rom, 4.4 rom (would give partition error but i replaced the flash_all.bat from a tutorial to bypass the partition erro) and the latest 6.0 chinese developer rom and it would finish successfully within under 100 seconds and would either go back to the cm13 bootloop or go to recovery and update cm13.
I tried QPST and emmc download with 4.4 rom and it would end with no error and go right back to bootlogo. tried flashing that rom with miflash and it would end within 80 seconds and go back to boot logo.
I tried QFIL with the latest miui8 chinese dev one with firehose and it would fail when it would go near userdata. dont remember the exact error but it was something like cannot divide by zero.
The ONLY time i could flash a different recovery is when i would use the same cm13update.zip and replace the recovery.img with another img such as cwm or mi stock recovery. when i used cwm, it would also try to install cm13 and fail as well.
I tried taking the battery off and shorting the two points which made it easier to get into EDL mode to try to use QPST with no luck.
among so many tries I booted to cm13 a few times. never could it go to homescreen though. once it would not go past the password lockscreen even if i put in the proper password and another time it would but ALL the apps would crash and i would not be able to even swipe the home screens.
sometimes when i tried flashing the cwm ota roms that was in the phone previously or the latest cm14 with otg usb, i would get
INSTALL ZIP SUCCESSFUL on top of twrp but the whole screen would fill up with red writing which said
Error opening : 'data/data/cyanogenmod.platform' (no such file or directory)
and the same thing about every app that was there on the phone.
i do not care about my files theyre all backed up. I just want to use the phone again. Any help is appreciated. thanks.
bump
Hello there, I can make and upload twrp backup of miui v8 dev version. Have you tried to restore a backup?
You'll have to make new partition for this backup ( there are so many threads like "extend partition mi3" or smth like that)
http://en.miui.com/thread-99430-1-1.html
Tried the ones from this thread?
http://forum.xda-developers.com/xia...instruction-to-restore-mi4-mi3-t3279927/page5