I tried updating my phone to v3.0 from v2.5 but failed, saying "flash failed", on the k3 note lenovo.
I used the manufacturers software to update, but it gave me that error, flash failed, doing that rom update.
It detected my device, but failed to update.
I restored it to it's original from rootjunkys videos. Unbricking the device.
Need help.
Wanna pimp my phone, but wanna update it first.
T.T this custom stuff is killing me....
Thanks
Related
Hello everyone. I am new to lg x4 but no new to android. Today i rooted the phone but when i installed the Recovery from rom manager I am getting a message when i am trying to accuse recovery saying bbot image signature error and phone restarts, Although i can get the mobile working after 10 restarts but i wanna try new roms ...
Unlock your bootloader, then root it and then install cwm, you should be on jb in order to do so. Refer stickies for how to.
I have a Consumer Cellular XT1064 running 21.11.17.titan_retuaws.retuaws.en.US.na with an unlocked bootloader and am having trouble applying the lollipop ota upgrade patch. When I attempt to apply the patch in stock recovery, I get an error durning "Patching system files". The error reads "assert failed: apply_patch(*/system/framework/framework-res.apk" followed by a series of letters and numbers, and ultimately ending with "installation aborted".
I previously successfully applied the ota and was running Lollipop using this guide. While attempting to root, I couldn't get twrp to persist after a full boot nor could I successfully install supersu, so I decided to start from scratch (probably a bad move) and followed those same steps again, but this time ran into the assert failed error described above. I tried re-locking the bootloader, thinking that may help, but got error messages during the process, so that's a no-go. I've scoured the forums and web for another solution, but haven't come up with anything so far.
Maybe there are some files/settings that aren't being completely restored to 4.4.4 stock through the manual flashing process? I can't get RSD Lite to recognize this phone (even though it recognizes my Droid Maxx just fine).
Any other thoughts or suggestions would be much appreciated.
Solution for XT1064 assert failed errors when applying Lollipop ota
After much trial and error, I successfully found a way to get rid of the assert failed errors and get back to Lollipop. Thanks to diamondjoker5, I obtained the original retail firmware 21.11.23 and used fastboot commands to flash it over the 21.11.17 firmware. I then let the phone fully boot into 21.11.23, powered off, then followed the original ota update procedure once again, without any errors.
Hi, first time posting here, forgive me if I'm doing something wrong...
I flashed Nougat beta (L19C432B322), regretted it, and now wanting to go back to EMUI 4.1.1 (before flashing, I was on L19C20B150). Trying to follow the steps for the Huawei official rollback package, but problem is I can't even get the intermediate package (C900B300) to work through dload method... update always fails at 5%.
I am unable to relock my bootloader using the SRK tool. The error I get is "remote: root type is risk".
My phone has never been rooted.
Any help would be greatly appreciated!!
Edit: Tried to flash L19C636B168 full rom using dload method. Now bootloader is locked, but no rom is installed, booting always gives erecovery. Unable to flash any recovery via fastboot.
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??
Greetings,
in a last month or so, im trying to revive this tablet, mostly because of the dual boot posibilities, but that can be done only with lollipop uefi bios.
My device is currently running 4.4 .201 OTA and im unable to update to 5.0 with whatever step i do.
First of all, i hard bricked my first device of this model myself completely, so i decided to replace my motherboard, somehow i lost the side buttons aswell, so i did order a "non-working" device from e-bay. I made it working by just flashing the .182 firmware.
I wasnt able to apply OTAs to the device, always got Status 7 Error in recovery, i did fix that by using a modified update script that i had to apply to every single OTA i flashed.
Finally got to 201, now its time to go to Lollipop.
I tried
- flashing LP firmware through temporary recovery (CWM/TWRP)
- flashing every single firmware thats available - .17; .24; .33; .36 - every single one with the KK "prefix"
- flashing every single firmware with the official firmware update method aswell (putting the update file to root of internal/sd memory and applying it within the tablets system
- flashing the official OTA updates that arrived as dlpkgfile
- flashing the firmware with the command file (putting renamed firmware to update.zip, to /data/ + command file to /cache/recovery/
- flashing service firmware with Intel Phone Flash Tool (KK/LP)
- reseting data/factory reset before and after the update, with cache included
- restoring both backups of KK/LP
- flashing boot.img extracted from the ROM after applying the update
Maybe im missing something, but in every single case, the update went through (some maybe had error in TWRP, but were fine in CWM/stock), but the system doesnt upgrade itself.
The update completes, then after a system reboot the device just goes to the ASUS logo (first one), gets stuck for roughly 30 seconds and bootloops. The droidboot/bootloader is not changing after update.
Any ideas on how to proceed now? I believe i tried every single method of updating, could not suceed unfortunately.
Thanks!
FIXED
The original system update process (putting update file in the root of sdcard,blablabla) always ended up on like 70% and rebooted, with no bootloader upgrade.
So the system didnt boot up, had to revert back to kitkat.
I found OTA Verifier app, that verifies the update script and selects the error in it.
I saw, its saying my device model number is K013_1, but thats not true! For some reason i had 2 build.props in my system files, so i rooted, deleted build.prop_K013_1 (or some name like this) and kept the original one.
! The update itself didnt give any kind of error, it went through without saying anything, thats why i didnt think the updater script would be the problem!
I believe, just deleting the first 2 lines in the update script would help aswell.
After that, i applied the update and waited for it to finish, at 70% once again it rebooted, but this time it started upgrading the bootloader. Lollipop installation finished and im finally at 5.0