Related
Hi Guys,
My Mi3 is bricked.I did a repartition some months back and I wanted to install MIUI 7.I used Miflash but it is showing size too large error while flashing.My recovery is replaced with stock recovery.I tried to use ADB to push the file,that is also not working as it is shoing device not found while I am in recovery.I installed Miphonemanager as well for that.But there is no luck.I am out of ideas.Can anyone please help me.
Can anyone let me know which driver I need to choose in driver manager for android in desktop? Currently I tried CMCC Composite ADB driver and Xiaomi Android Interface.
Flash latest TWRP first. What happened during repartition?
You can allways acces the eeprom writer through short circuiting the sim card, there are a lot of tutorials, the only way to brick this phone is breaking its hardware
nsakhare said:
Hi Guys,
My Mi3 is bricked.I did a repartition some months back and I wanted to install MIUI 7.I used Miflash but it is showing size too large error while flashing.My recovery is replaced with stock recovery.I tried to use ADB to push the file,that is also not working as it is shoing device not found while I am in recovery.I installed Miphonemanager as well for that.But there is no luck.I am out of ideas.Can anyone please help me.
Can anyone let me know which driver I need to choose in driver manager for android in desktop? Currently I tried CMCC Composite ADB driver and Xiaomi Android Interface.
Click to expand...
Click to collapse
Install custom recovery through fast boot mode... Then flash the repartition revert zip .. There is one revert zip in miui forum which ends like this "....EIPerroVerde". Only this revert zip works..Then use miflash .. It should work..
Sent from my MI 3W using Tapatalk
aniketkuber said:
Install custom recovery through fast boot mode... Then flash the repartition revert zip .. There is one revert zip in miui forum which ends like this "....EIPerroVerde". Only this revert zip works..Then use miflash .. It should work..
Sent from my MI 3W using Tapatalk
Click to expand...
Click to collapse
The correct repartition zips can be found in the thread in my signature.
Reproduced here for Tapatalk or mobile users:
http://forum.xda-developers.com/xiaomi-mi-3/general/extremely-useful-flashable-zips-t3080860
The Dork Knight Rises said:
The correct repartition zips can be found in the thread in my signature.
Reproduced here for Tapatalk or mobile users:
http://forum.xda-developers.com/xiaomi-mi-3/general/extremely-useful-flashable-zips-t3080860
Click to expand...
Click to collapse
Hey Knight (didn't want to call you Dork :angel: )
I have a messed up phone,
2 questions here :
1- Would repartitioning reset ALL the partitions ?
2- When installing a ROM with fastboot, will ALL the partitions be filled with the necessary data ?
(I'm in doubt because of IMEI data)
Btw, can anyone point me to a link with WORKING fastboot ROM downloads ?
Inonotting said:
Hey Knight (didn't want to call you Dork :angel: )
I have a messed up phone,
2 questions here :
1- Would repartitioning reset ALL the partitions ?
2- When installing a ROM with fastboot, will ALL the partitions be filled with the necessary data ?
(I'm in doubt because of IMEI data)
Btw, can anyone point me to a link with WORKING fastboot ROM downloads ?
Click to expand...
Click to collapse
Repartitioning will wipe both your system partitions [EDIT: Seems I was wrong?]. If you want to use MIUI 7, you can use either extended partition, or stock partition using the zip from my link.
For fastboot I guess you'll need stock.
No, installing a MIUI fastboot ROM shouldn't touch your IMEI. But yeah everything else can be overwritten, depending on which bat file you use when flashing.
The process I'd recommend right now is to flash TWRP IMG using fastboot(use the 15-second ADB installer and look up a tutorial on how to flash an IMG. Basically just put the IMG into the adb/fastboot installation directory and then open a terminal window and then fastboot flash)
And as for MIUI fastboot ROM, you just gotta find the thread on MIUI forums. Google can help
The Dork Knight Rises said:
Repartitioning will wipe both your system partitions. If you want to use MIUI 7, you can use either extended partition, or stock partition using the zip from my link.
For fastboot I guess you'll need stock.
No, installing a MIUI fastboot ROM shouldn't touch your IMEI. But yeah everything else can be overwritten, depending on which bat file you use when flashing.
The process I'd recommend right now is to flash TWRP IMG using fastboot(use the 15-second ADB installer and look up a tutorial on how to flash an IMG. Basically just put the IMG into the adb/fastboot installation directory and then open a terminal window and then fastboot flash)
And as for MIUI fastboot ROM, you just gotta find the thread on MIUI forums. Google can help
Click to expand...
Click to collapse
Thanks ... but ....
I was under the impression that there were many more partitions (about 28).
Check this site:
http://en.miui.com/thread-138246-1-1.html
Basically, I'm looking for an easy way out to make a REAL factory reset from PC.
Inonotting said:
Thanks ... but ....
I was under the impression that there were many more partitions (about 28).
Check this site:
http://en.miui.com/thread-138246-1-1.html
Basically, I'm looking for an easy way out to make a REAL factory reset from PC.
Click to expand...
Click to collapse
Well there ARE a LOT of partitions on any device, but the important ones are system, boot, data, cache, modem etc.
That guide seems to manually mess with the partition table, so it gets down and dirty.
The easiest thing would be to do what I said, flash TWRP or CWM r7 by furniel and then the proper stock partition zip. Then use MiFlash or recovery to flash any ROM.
I think I'm back online
The Dork Knight Rises said:
Well there ARE a LOT of partitions on any device, but the important ones are system, boot, data, cache, modem etc.
That guide seems to manually mess with the partition table, so it gets down and dirty.
The easiest thing would be to do what I said, flash TWRP or CWM r7 by furniel and then the proper stock partition zip. Then use MiFlash or recovery to flash any ROM.
Click to expand...
Click to collapse
OK,
I followed your links and flashed :
First : Repartition to Stock Layout
Then : Repartition to 1.2GB Single System
Strange, after this, I did a normal reboot, it rebooted into my old ROM.
Shouldn't that have been erased after partitioning ?
Anyway,
Then I flashed ; update-XenonHD-08-08-15-signed-.zip
WAIT WAIT .....
as I'm typing, I'm flashing update-XenonHD-09-05-15-signed-cancro.zip,
first ROM in a few weeks that seems to be installing.
Let me check is it really installed .... YEP .... progress
Flashing : pa_gapps-modular-pico-5.1-20150418-signed
Everything seems to be going smooth
OK, for the time being .... all good.
Thanks a lot :good:
If your device cannot boot, flash it thru fastboot mode. See the full detailed tutorial on en.miui.com
Well you can directly flash with miflash even with the extended partition. Just edit the fastboot script (.bat extension with windows) and search for line
fastboot flash system+system1
And then delete system1
Fastboot flash system
And use those script for flashing via miflash
I have a rare phone running Android 6.0 on a MT6750 with an unlocked bootloader (might be MT6750T since it is 1920x1080, but the only things I have found say MT6750)
I have been unable to get TWRP working on this phone after trying several porting guides and TWRP images. Almost all port attempts result in the boot image (logo.bin - android logo), followed by a black screen for a few seconds, then it reboots into Android.
Is it possible to manually patch the boot.img to gain root? If so, can someone point me to a guide for it? I found https://forum.xda-developers.com/android/software-hacking/systemless-root-mediatek-t3309909 but PATH doesnt seem to be set anywhere in my boot image (grep -nrw 'boot.img-ramdisk' -e "PATH"). I tried adding "export PATH $PATH:/data/bin" or "export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin::/data/bin" to init.environ.rc with other exports, but I get a boot loop
try recompile the decompiled boot.img without doing any changes and flash the compiled boot.img to see that there is no problem with respect to compilation of boot.img
shankar_vl said:
try recompile the decompiled boot.img without doing any changes and flash the compiled boot.img to see that there is no problem with respect to compilation of boot.img
Click to expand...
Click to collapse
i decompiled and recompiled without any changes using kitchen tools and flashed back ... but its showing error.
same with recovery.img also
btw im using oppo f3 mt6750t
rajeshca911 said:
i decompiled and recompiled without any changes using kitchen tools and flashed back ... but its showing error.
same with recovery.img also
btw im using oppo f3 mt6750t
Click to expand...
Click to collapse
Then its a compilation error. Its not being compiled correctly.
Btw, systemless root by supersu and magisk do a lot things like starting sudaemon, injecting supolicy changes, mounting su.img, etc. Its better to port a custom recovery and let supersu or magisk zip do all the required things to root your device.
Or if you want to be ambitious, dirty your hands with hackings, unzip these zip files and try to implement manually what is programmed there.
My suggestion is go for porting recovery from devices matching your device specs ( need not be 100%). There are several threads on this forum helping you out on this. I think chances of porting a workable custom recovery are brighter than manually compiling su compatible boot.img.
There's the problem..
I did port custom recovery.
But when I flash it back to device it's showin error.
I understand that I need to dirt my hands more to get root my device
So I decided to compile revovery.. But oppO f3 source files r not available. I tried with omni Tom source. But it failed
rajeshca911 said:
i decompiled and recompiled without any changes using kitchen tools and flashed back ... but its showing error.
same with recovery.img also
btw im using oppo f3 mt6750t
Click to expand...
Click to collapse
rajeshca911 said:
There's the problem..
I did port custom recovery.
But when I flash it back to device it's showin error.
I understand that I need to dirt my hands more to get root my device
So I decided to compile revovery.. But oppO f3 source files r not available. I tried with omni Tom source. But it failed
Click to expand...
Click to collapse
You said that even the imgs just compiled without any changes made to decompiled files are not able to boot. Then there must be something wrong with compiling. Your tools for compiling may not be correctly working.
There are carlive image kitchen tools. get them here https://forum.xda-developers.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658. They are known for flawless working.
What is more important now is that you have right tools for compiling imgs. Then you can think of further.
shankar_vl said:
You said that even the imgs just compiled without any changes made to decompiled files are not able to boot. Then there must be something wrong with compiling. Your tools for compiling may not be correctly working.
There are carlive image kitchen tools. get them here https://forum.xda-developers.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658. They are known for flawless working.
What is more important now is that you have right tools for compiling imgs. Then you can think of further.
Click to expand...
Click to collapse
Thanks bro. But im using carliv kitchen tools only.
I didn't tried with other kitchen tools yet.. So i give a try other tools
rajeshca911 said:
Thanks bro. But im using carliv kitchen tools only.
I didn't tried with other kitchen tools yet.. So i give a try other tools
Click to expand...
Click to collapse
no need. carliv tools are perfect. stick with them.
are you able to successfully flash imgs with sp flash tools? no matter whether you are able to boot with them.
as for porting, use twrp or any other custom recovery of SoC as yours, mt6750t and of OS version similar to yours as well.
shankar_vl said:
no need. carliv tools are perfect. stick with them.
are you able to successfully flash imgs with sp flash tools? no matter whether you are able to boot with them.
as for porting, use twrp or any other custom recovery of SoC as yours, mt6750t.
Click to expand...
Click to collapse
Ok.. I stick with carliv as u suggested. And... Yes... Im able to flash img files to phone but not with sp flash tools. Im using professional tools ( uni tools from volcano) and also flashing using a cracked download tool meant for oppo devices. ( the download tool was created on base of sp flash tools only)
Then...
I just tried twrp porting only ( same soc mt6750t quitel k6000 plus i think.. Which chipset is mt6750t)
Also tried with oppo f1s twrp which chipset is mt6750.. ( not 6750t.. ) both went wrong..
seniors and xda developrs ( zackie& a guy from Indonesia unfortunately i forgot his name) also tried to. Port twrp for me. I also tried flashing their img files ..everything went not well.. There i have understood that either compiling or flashing causing error in my device
Thats y im trying to find other wayz.. There i found ur thread .& fetching useful checklist:good:
rajeshca911 said:
Ok.. I stick with carliv as u suggested. And... Yes... Im able to flash img files to phone but not with sp flash tools. Im using professional tools ( uni tools from volcano) and also flashing using a cracked download tool meant for oppo devices. ( the download tool was created on base of sp flash tools only)
Then...
I just tried twrp porting only ( same soc mt6750t quitel k6000 plus i think.. Which chipset is mt6750t)
Also tried with oppo f1s twrp which chipset is mt6750.. ( not 6750t.. ) both went wrong..
seniors and xda developrs ( zackie& a guy from Indonesia unfortunately i forgot his name) also tried to. Port twrp for me. I also tried flashing their img files ..everything went not well.. There i have understood that either compiling or flashing causing error in my device
Thats y im trying to find other wayz.. There i found ur thread .& fetching useful checklist:good:
Click to expand...
Click to collapse
As you tried various flashing methods, you might have already known all the related intricasies of flashing. still I just want to mention that I presume you might have then known vcom drivers, creating scatter file with mtkdroid tools, loading scatter file and, most importantly switching off phone and plugging phone to PC just after clicking on flash button in sp flash tool.
And about the other tools of flashing you mentioned, sorry I will not be helpful.
A thing to mention regarding porting is taking care of mount points in fstab file and a similar file if any at /etc folder in ramdisk of decompiled port recovery. mount points should be same as fstab of your boot.img.
Besides, ensure kernel (Imaze) of port recovery is replaced with that of boot.img.
shankar_vl said:
As you tried various flashing methods, you might have already known all the related intricasies of flashing. still I just want to mention that I presume you might have then known vcom drivers, creating scatter file with mtkdroid tools, loading scatter file and, most importantly switching off phone and plugging phone to PC just after clicking on flash button in sp flash tool.
And about the other tools of flashing you mentioned, sorry I will not be helpful.
A thing to mention regarding porting is taking care of mount points in fstab file and a similar file if any at /etc folder in ramdisk of decompiled port recovery. mount points should be same as fstab of your boot.img.
Besides, ensure kernel (Imaze) of port recovery is replaced with that of boot.img.
Click to expand...
Click to collapse
Your not helpfull??.. I don't agree with that. May be im Not in the position to catch your mind.
However.. Im not going to miss single chance to upgrade myself ( yes ofcourse from devs n seniors like u)
As you said
1) i have installed vcom drivers & fetched scatter file. ( again not from mtk droid tools) . I heard mtkdroid tools nOt fully supporting mt67xx Series. Even i tried modified mtkdroid tools developed by dev havoc.. And droid tool showed some info like cpu info.. Etc. But right hand side there was an error which saying that its usable to fetch info. . I presume the error may b causing by oppo. Own OS ( Color OS based on android 6.0).. And my last try was 2 months ago. So i dont know if there is any improvements in droid tools or not. Please privide me links if they updated/ supported 67xx series
2)yes i agree with mount points you mentioned. I was just replacing fstab file from stock to. Port. I didnt edit any. . I will check again and update u.
3) Actually im in dilemma to blame on cimpiling or flashing.. The device is not booting even i didn't modify any item after repack. I need solution for that. If that resolved... Automatically everything will b set up by themselves.. Pls share any views regarding this..
I know its difficult to u to guide until u have hands on it or personally seen d procedures & results
I may upload videos / pictures/ share Team viewer etc.. if u want to see it personally.. So.. U can better understand my problem , my flaws where i need to b improved ( onlynif u wish) however i need a mentor to guide n judge methods im following
rajeshca911 said:
Your not helpfull??.. I don't agree with that. May be im Not in the position to catch your mind.
However.. Im not going to miss single chance to upgrade myself ( yes ofcourse from devs n seniors like u)
As you said
1) i have installed vcom drivers & fetched scatter file. ( again not from mtk droid tools) . I heard mtkdroid tools nOt fully supporting mt67xx Series. Even i tried modified mtkdroid tools developed by dev havoc.. And droid tool showed some info like cpu info.. Etc. But right hand side there was an error which saying that its usable to fetch info. . I presume the error may b causing by oppo. Own OS ( Color OS based on android 6.0).. And my last try was 2 months ago. So i dont know if there is any improvements in droid tools or not. Please privide me links if they updated/ supported 67xx series
2)yes i agree with mount points you mentioned. I was just replacing fstab file from stock to. Port. I didnt edit any. . I will check again and update u.
3) Actually im in dilemma to blame on cimpiling or flashing.. The device is not booting even i didn't modify any item after repack. I need solution for that. If that resolved... Automatically everything will b set up by themselves.. Pls share any views regarding this..
I know its difficult to u to guide until u have hands on it or personally seen d procedures & results
I may upload videos / pictures/ share Team viewer etc.. if u want to see it personally.. So.. U can better understand my problem , my flaws where i need to b improved ( onlynif u wish) however i need a mentor to guide n judge methods im following
Click to expand...
Click to collapse
I empathize with your frustration.
Truth is that with the devices which have not caught the fancy of developers, not having proven root methods, custom recovery, etc only, we take initiatives ourselves and learn the things the hard way which is essentially a true way learning. With popular devices having already so many developments, there is no scope for adventurism and fun as well.
Just see back what are all you gained in doing the things you did with your device for gaining root. Could it have been possible with the so called popular devices?
Now let's come to the issue. In all times of failed booting on compiled imgs, how did you restore them? flashing again stock boot and recovery imgs? and with tools you mentioned?
If you could flash stock boot and recovery with the tools you mentioned, then there is no problem with those flashing tools. Then it comes to the decompiling and recompiling of imgs.
If it could be possible, can you share here stock boot.img, and custom recovery you have selected for porting (also mention the device name, recovery pertained). Let me try.
Yup.. Bro.
What have you said all true.. during this journey i have learned so manythings like porting custom recovery , read back firmware etc and i cant forget what i have learned.. so many trail and errors
below link is the stock and custom recovery i tried to port
https://drive.google.com/file/d/0B6wWbhnrRZ_-V2RZQXByYjc4QVU/view?usp=drive_web
and a developer also tried to to port recovery for me .. below is the link which he modified for me
https://www.androidfilehost.com/?fid=745425885120760137
Im also enclosing stock boot.img
https://mega.nz/#!MF1ySQ4D!ku6RWfOP8QTkm75sNq_1_n-_Af0y843J0I0tiCHRa8k
My Device Details are
Manufacture : Oppo
Device name : Oppo f3
Model No : CPH1609
chipset : MT6750T , 4gb Ram , 64 Gb storage
[ I Really praying Inside ....:angel: god may give result for our endless efforts }
@rajeshca911 can you give details for the custom recovery you have given links, like name of the device, its os ( lollipop, marshmallow, like), and chipset if possible, it pertained to.
shankar_vl said:
@rajeshca911 can you give details for the custom recovery you have given links, like name of the device, its os ( lollipop, marshmallow, like), and chipset if possible, it pertained to.
Click to expand...
Click to collapse
Aquired custom recovery from
Device : qukitel K6000 plus, chipset MT6750T
android version 6.0 (from below)
https://www.google.co.in/amp/s/foru...al/oukitel-k6000-plus-twrp-root-t3620241/amp/
rajeshca911 said:
Aquired custom recovery from
Device : qukitel K6000 plus, chipset MT6750T
android version 6.0 (from below)
https://www.google.co.in/amp/s/foru...al/oukitel-k6000-plus-twrp-root-t3620241/amp/
Click to expand...
Click to collapse
I think the signature of the boot.img gets changed. Try to sign it after decompiling and recompiling by AVB patcher from here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
anandverma458 said:
I think the signature of the boot.img gets changed. Try to sign it after decompiling and recompiling by AVB patcher from here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
Shall i sign both boot.img and recovery.img as well?? or is it enough to sign compiled recovery.img ?
---------- Post added at 07:57 AM ---------- Previous post was at 07:44 AM ----------
i generated public and private keys also signed and generated
boot_signed.img
recovery_signed.img
first i flashed both the images... result was soft brick and i had to flash original boot.img
second i flashed only signed recovery.img and same was repeated.
rajeshca911 said:
Shall i sign both boot.img and recovery.img as well?? or is it enough to sign compiled recovery.img ?
---------- Post added at 07:57 AM ---------- Previous post was at 07:44 AM ----------
i generated public and private keys also signed and generated
boot_signed.img
recovery_signed.img
first i flashed both the images... result was soft brick and i had to flash original boot.img
second i flashed only signed recovery.img and same was repeated.
Click to expand...
Click to collapse
Actually, I had the same problem (I have vivo 1603). When I flashed boot.img after decompiling and recompiling,it bootlooped. I had twrp installed, so I first restored the backup of stock boot.img, and then installed the recompiled boot.img without rebooting. That worked for me
As you don't have custom recovery, I suggest that you first flash stock boot.img, and after the process completes, flash the recompiled boot.img without rebooting your device.
Hey bro, I decompiled the stock boot.img to see that if 'verify' flag was preventing booting the system with other than stock recovery. Dm-verity is a recent security control for preventing booting with changed/modified kernel/system. But I could not find any such flags, but found verity_key, so I just deleted it and decompiled the boot.img. I am not sure whether it can solve your booting problem. Let's see will this now allow to boot with custom kernel. Here is the modified stock boot.img. http://www.mediafire.com/file/tc1k1ghmy76nfqd/modified_oppo_boot.img
Flash first this boot.img and then flash the custom recovery.imgs (you can try your recoveries also)
I have also ported two recovery.imgs. Both are ported from the twrps for the same device, K6000 plus. However, what I found for this k6000 plus was different in size. So I ported two twrp recovery imgs. Here are two twrp ported recoveries, one is from you have given links to and another is from what I found on this forum.
http://www.mediafire.com/file/4als7qmpwdz1iv4/oppo_port_twrpv1.img
http://www.mediafire.com/file/5xz7387at6rr0dy/oppo_port_twrpv2.img
Once again, I reiterate that first flash the modified boot.img and then try flashing the recoveries.
Best of luck
anandverma458 said:
Actually, I had the same problem (I have vivo 1603). When I flashed boot.img after decompiling and recompiling,it bootlooped. I had twrp installed, so I first restored the backup of stock boot.img, and then installed the recompiled boot.img without rebooting. That worked for me
As you don't have custom recovery, I suggest that you first flash stock boot.img, and after the process completes, flash the recompiled boot.img without rebooting your device.
Click to expand...
Click to collapse
Bro thanks for your advice.. and i did same what you have said.. i flashed stock boot.img with out rebooting flashed recompiled boot.img the device didnt boot up.. i think culprit is something else .. that prevets booting custom images
TWRP from TWRP Builder builded for Nokia 7 Plus....
I still don't know if working (as i write in another thread), so that it does not fit, i write separate thread about it...
Small story:
I unpacked B2N-132E-0-00WW-B07.nb0 using nbd tools, although is not complete unpacked, "B2N-0-132G-00WW-boot.img" is here...
Unpack using unmkbootimg and get kernel(zImage) and ramdisk(ramdisk.cpio.gz)...
In unpacked ramdisk is binary "recovery", "init.recovery.qcom.rc" and "recovery.fstab" which is used/imported by default "init.rc"...
Then i think this is recovery, using TWRP Builder APK installed on N7+ i upload this image...
After some days i receive message that TWRP for Nokia 7 Plus is builded OK
Of course flashing this need Unlocked bootloader, then all who need it, PLEASE do participate in petition about Unlocking bootloader:
https://forum.xda-developers.com/nokia-7-plus/how-to/petition-possibility-to-unlock-t3788953
(after write comment, please also click too on "Do you have this question as well?")
Download: TWRP_onyx_00ww-08051830.img
Won't boot (tried to boot into it via fastboot (I don't want to flash it yet), and it just hanged on the android one text. Maybe going to properly flash it in few days.
Ranpe said:
Won't boot (tried to boot into it via fastboot (I don't want to flash it yet), and it just hanged on the android one text. Maybe going to properly flash it in few days.
Click to expand...
Click to collapse
thanks for testing, flashing is sure not need and not safe, boot via fastboot i think must work(if twrp working)...
anyway if you can boot then you have unlocked bootloader right?
can you try boot via fastboot original in nb0 boot/recovery from twrp is builded? file B2N-0-132G-00WW-boot.img
maybe problem is that this is "hybrid" boot+recovery in one, and is need some hotkey or magic durring boot?
k3dar7 said:
thanks for testing, flashing is sure not need and not safe, boot via fastboot i think must work(if twrp working)...
anyway if you can boot then you have unlocked bootloader right?
can you try boot via fastboot original in nb0 boot/recovery from twrp is builded? file B2N-0-132G-00WW-boot.img
maybe problem is that this is "hybrid" boot+recovery in one, and is need some hotkey or magic durring boot?
Click to expand...
Click to collapse
Yeah, I have unlocked bootloader on my 7+. Looks like the boot.img (which's used in that build of TWRP) is from older rom than the one I'm on at the moment. (B2N-213B-0-00WW-boot.img) May it be the reason for it to not boot? Anyway, I'll try to build a newer version soon.
Ranpe said:
Yeah, I have unlocked bootloader on my 7+. Looks like the boot.img (which's used in that build of TWRP) is from older rom than the one I'm on at the moment. (B2N-213B-0-00WW-boot.img) May it be the reason for it to not boot? Anyway, I'll try to build a newer version soon.
Click to expand...
Click to collapse
How did you get it open? Bootloader
DroiDMester said:
How did you get it open? Bootloader
Click to expand...
Click to collapse
https://forum.xda-developers.com/nokia-6/how-to/guide-how-to-unlock-bootloader-qualcomm-t3769930/
Ranpe said:
Yeah, I have unlocked bootloader on my 7+. Looks like the boot.img (which's used in that build of TWRP) is from older rom than the one I'm on at the moment. (B2N-213B-0-00WW-boot.img) May it be the reason for it to not boot? Anyway, I'll try to build a newer version soon.
Click to expand...
Click to collapse
yes, TWRP in #0 is builded from *boot.img from 8.0, i not find newer version, you have B2N-213B-0-00WW-boot.img ? if yes, then please try upload it via TWRP Builder, i not this do because not have newer file and too not posible to upload more that 1x from one device...
unlocking bootloader you do via NTool?
k3dar7 said:
yes, TWRP in #0 is builded from *boot.img from 8.0, i not find newer version, you have B2N-213B-0-00WW-boot.img ? if yes, then please try upload it via TWRP Builder, i not this do because not have newer file and too not posible to upload more that 1x from one device...
unlocking bootloader you do via NTool?
Click to expand...
Click to collapse
I've submitted the newer boot.img to them already, we'll see if they update it. Yeah, unlocked via ntool (by a guy I know).
Ranpe said:
I've submitted the newer boot.img to them already, we'll see if they update it. Yeah, unlocked via ntool (by a guy I know).
Click to expand...
Click to collapse
strange, i not see it in complete, queue, running or rejected don't show after upload you some error like "for this device is already builded"? i don't know if is posible rebuild for same device model from another device with another/newer boot.img...
I thought too about NTool, but i not find any seller od setool2 credit with small amount of credit (<=10), only 30 and for me message no answer... also authot of NTool write me only "not help you"... then try wait what Nokia do with many question about posibility of unlocking bootloader officialy...
try to get stock recovery img, porting should be easier.
SkaboXD said:
try to get stock recovery img, porting should be easier.
Click to expand...
Click to collapse
as i say in #0 TWRP is builded from srock recovery from 8.0 NB0 for N7p, i think problem is that N7p not use separate recovery but is inside normal boot, then need some magic to switch to recovery part of this "hybrid" boot, and because N7p need to recovery via powering cable and hold VolUp+Power then i think is same need with booting TWRP from #0, but who know if this is possible with not flashed booting via fastboot...
edit: anyway if my thoughts are true, then with hybrid boot+recovery flashed to device, is really need twrp based on exact boot image for current rootfs on device... (as Rampe too say if is possible evoce recovery from image booted via fastboot without flashing, then is not need exact version...
SkaboXD said:
try to get stock recovery img, porting should be easier.
Click to expand...
Click to collapse
The recovery is in the boot.img, and we have the images already.
Ranpe said:
The recovery is in the boot.img, and we have the images already.
Click to expand...
Click to collapse
oh i get it, so you need to make twrp for every Android version because of changed boot.img?
SkaboXD said:
oh i get it, so you need to make twrp for every Android version because of changed boot.img?
Click to expand...
Click to collapse
Not 100% sure of it, but unfortunately it may be so.
SkaboXD said:
oh i get it, so you need to make twrp for every Android version because of changed boot.img?
Click to expand...
Click to collapse
if changed kernel version/config (or binary, script, key in boot.img) then yes... if update use same files in boot.img as previous then no...
if i look at version in Settings/About for 8.1 v2.13 and 8.1 v2.22 then kernel version i same 4.4.78, but builded date is other (17.3. and 20.4.), not know if changes config, source etc, or is only same kernel rebuilded with full build proces again... i not have whole boot.img for 2.13 or 2.22 only for 8.0 v1.23
edit: FW for camera/touch/baseband/nothing not in boot.img (if not compile inside kernel(which i do not expect))
@Ranpe you have boot.img for 2.13 and/or 2.22 ? can you please upload it somewhere?
k3dar7 said:
@Ranpe you have boot.img for 2.13 and/or 2.22 ? can you please upload it somewhere?
Click to expand...
Click to collapse
Yeah, I have the boot.img for 2.13, but not (yet) for 2.22 (Need to get python working properly so I could dump inside of the payload.bin in the new OTA-update). You can download the 2.13 boot.img (and some other stuff) from here.
dotsaredots said:
Yeah, I have the boot.img for 2.13, but not (yet) for 2.22 (Need to get python working properly so I could dump inside of the payload.bin in the new OTA-update). You can download the 2.13 boot.img (and some other stuff) from here.
Click to expand...
Click to collapse
thanks for uploading, i now too have extracted 2.13 using payload_dumper.py (link from here), but for unpack payload.bin from 2.22 i think do not help any python "propertly working" because 2.22 is incremental update and this is not supported by payload_dumper.py...
btw: now i'm sure that N7p have really hybrid recovery_in_boot, what is used for any Phone that use new A/B method of updating on running system and simply switch to new update after reboot...
https://source.android.com/devices/tech/ota/ab/ab_implement
first of all you need to edit recovery.fstab in vendor partion it won`t boot because of encrypted data
The Moto X4 (payton) too has a hybrid recovery and they managed to make twrp. Might contact @mightysween or the official maintainers at twrp for hints?
Broadcasted from Zeta Reticuli
Gravemind2015 said:
The Moto X4 (payton) too has a hybrid recovery and they managed to make twrp. Might contact @mightysween or the official maintainers at twrp for hints?
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
X4, Pixel2 and other A/B devices use a bootable recovery image (fastboot boot twrp.img) and then install a .ZIP package that patches the boot.img with TWRP recovery.
There have been other issues on the various devices with encryption, with bootcontrol partition switching, and with handling of empty "B" partitions. So proceed with caution, especially with flashing roms from TWRP before you have a way to populate the B partition.
Hello everyone :laugh:!
Tried rooting the Nokia 4.2, did not know which img to use exactly so I tried one from some other shady site and messed up. Luckily, the recovery partition was still working. After trying to boot lots of images, I got tired and accidentally even flashed a Nokia 6.2 TWRP image to my recovery partition. Then I completely messed up. The phone only gets into fastboot now. May I please ask some help of you? I've been trying for days to fix things. I just wanted to root the original firmware. Now when I try to flash TWRP, it even says that the 'recovery' partition has no partition table! I can still write to boot_a and boot_b though. The phone originally had the October patch level, but before bricking it I upgraded it to the December level.
Kind regards,
Alexander47u
Search on google and try do download and flash the stock firmware (unrooted)
Phone does not get detected by QFIL
thegamingcat13 said:
Search on google and try do download and flash the stock firmware (unrooted)
Click to expand...
Click to collapse
I have tried this using QFIL, however the phone is not detected. The phone also goes into fastboot as soon as the cable is plugged in, even when the phone is off.
Have also installed appropiate drivers for QFIL, but no luck.
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Works, Thank you!
thegamingcat13 said:
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Click to expand...
Click to collapse
Thank you! This worked flawlessly.
#metoo
Haha, I have done the EXACT same thing as you. Now I can only enter fastboot mode and when I try to flash anything I have downloaded I get an error about missing partitions. I have looked everywhere for details on the partition sizes, mount points and so on but nobody has uploaded the information. In the end I went and purchased a second device in order to dump the entire stock ROM in order to fix the first phone. I've got the second phone running in ADB-mode but I can only backup to an .ab file so now I am back at square one. All of the guides I can find on how to dump the ROM involves flashing TWRP recovery but THERE IS NONE FOR THE 4.2 :crying: And after researching Android forensics I have found a guide to dumping the ROM but it needs root access in the phone shell. All I wanted was root (and LineageOS). Does anyone feel like patching the stock ROM and making a zip-file containing the img-files from all of the partitions?
Hi. You need to check which slot is in use, A or B. You can also choose slot A or B with fastboot. Then you flash the images to the partitions by appending _a or _b to the partition name.
E.g.
fastboot --set-active=a
fastboot flash boot_a boot.img
Etc.
You also need to make sure you have a recent version of fastboot, as the fastboot in some Linux package managers or blog posts for Windows give you the older one, which does not support changing active slots.
Inside the stock rom that can be found online, there is another archive containing the needed images.
alexander47u said:
Hi. You need to check which slot is in use, A or B. You can also choose slot A or B with fastboot. Then you flash the images to the partitions by appending _a or _b to the partition name.
E.g.
fastboot --set-active=a
fastboot flash boot_a boot.img
Etc.
You also need to make sure you have a recent version of fastboot, as the fastboot in some Linux package managers or blog posts for Windows give you the older one, which does not support changing active slots.
Inside the stock rom that can be found online, there is another archive containing the needed images.
Click to expand...
Click to collapse
Thanks for the tip! Looks like I solved it earlier, I found a "user_update" zip in one of the downloaded ROMs and used fastboot update user_update.zip. Wuhu! I did not specify the slot but the system boots up. On the first boot I got an error message asking me to restore factory settings which seemed to work. Now all I need to do is get root access... Alexander, did you manage to flash a rooted recovery now? Thanks in advance!
You need to put the stock boot.img unaltered on a sdcard or the internal storage and then run the Magisk android app. It will offer an option to patch the boot.img. Then you can place the patched boot.img back on your computer and flash it using fastboot.
alexander47u said:
You need to put the stock boot.img unaltered on a sdcard or the internal storage and then run the Magisk android app. It will offer an option to patch the boot.img. Then you can place the patched boot.img back on your computer and flash it using fastboot.
Click to expand...
Click to collapse
I was able to succesfully patch boot.img with magisk, then I copied the patched boot image to my computer with linux. Fastboot flash boot boot.img worked but upon reboot I got an error message saying "corrupt data" and offered to do a factory reset. Any chance you can upload your patched boot image so I can use yours?
Magisk boot.img patched.
http://s000.tinyupload.com/index.php?file_id=49342816027254664129
Posted
alexander47u said:
Magisk boot.img patched.
http://s000.tinyupload.com/index.php?file_id=49342816027254664129
Click to expand...
Click to collapse
You legend! Thank you. Now to see if I can get it to work... what security patch is this up to?
Oslokalle said:
You legend! Thank you. Now to see if I can get it to work... what security patch is this up to?
Click to expand...
Click to collapse
Up to March. I used the stock rom that is floating around on the internet. Not sure if I am allowed to post stock roms.
I was able to update to April using Magisk but not any further than that.
thegamingcat13 said:
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Click to expand...
Click to collapse
Tried this using a user_update.zip file from www[.]getdroidtips[.]com/stock-rom-nokia-4-2-firmware/. My phone boots again, but Wi-Fi doesn't work. My model # is TA-1133. What should I do?
Edit: tried to install the latest security OTA from t[.]me/nokiarepoen/379, V2.29C, but I get
Code:
E:Package is for source build 00WW_2_29B but expected 00WW_1_17I
. Is there a base user_update for build 00WW_2_29B floating around?
Oslokalle said:
Thanks for the tip! Looks like I solved it earlier, I found a "user_update" zip in one of the downloaded ROMs and used fastboot update user_update.zip. Wuhu! I did not specify the slot but the system boots up. On the first boot I got an error message asking me to restore factory settings which seemed to work. Now all I need to do is get root access... Alexander, did you manage to flash a rooted recovery now? Thanks in advance!
Click to expand...
Click to collapse
Kindly provide me that zip too.
Hi everyone,
I have some months before accidentally reset after ota update on magisk and lost root. Unfortunately I cant find this FW anywhere since it was almost immediatly been replaced by 10.0.16, and the only thread having such old firmware was using filehosting from which the links expired.
I tried doing a system ota, but it won't work. I don't expect anyone to extract the boot.img for me just share the 10.0.14. if available, i would prefer not to wipe system data, since now without root i can't backup, and Helium is no longer supported.
Thank You.
Ikarus01 said:
Hi everyone,
I have some months before accidentally reset after ota update on magisk and lost root. Unfortunately I cant find this FW anywhere since it was almost immediatly been replaced by 10.0.16, and the only thread having such old firmware was using filehosting from which the links expired.
I tried doing a system ota, but it won't work. I don't expect anyone to extract the boot.img for me just share the 10.0.14. if available, i would prefer not to wipe system data, since now without root i can't backup, and Helium is no longer supported.
Thank You.
Click to expand...
Click to collapse
OTA updates usually don't touch the boot image so you could use the fastboot or recovery ROM V10.0.13.0 from here https://flashxiaomi.com/download-install-miui-rom-for-xiaomi-mi-a2-all-miui-firmwares/ also you can flash a recovery and backup your boot image to patch it through Magisk or flash directly the zip (a lower version)
SubwayChamp said:
OTA updates usually don't touch the boot image so you could use the fastboot or recovery ROM V10.0.13.0 from here https://flashxiaomi.com/download-install-miui-rom-for-xiaomi-mi-a2-all-miui-firmwares/ also you can flash a recovery and backup your boot image to patch it through Magisk or flash directly the zip (a lower version)
Click to expand...
Click to collapse
Thank you for replying,
i thought about it but if it proves not the case, and they changed the hex i wouldnt like bootloops or problems down the road. If it works i will try to backup and go to latest android 9, since many are complaining about version 10 with emmc apparently forgotten.
Also unfortunately i lost twrp, and don't have a sd cardfor flashing,and wouldn't like to wipe data to install twrp.
I thought about it and my only course of action is getting the boot.img, dd is out of option since I am not rot, is there a non root way to unpack if it turns out 10.0.13 causes a bootloop?
Sorry if some things don't make sense I am getting back to this after a long hiatus, can I still extract the img. from zip, or do I have to upack it with python?
Thank you.
Ikarus01 said:
Thank you for replying,
i thought about it but if it proves not the case, and they changed the hex i wouldnt like bootloops or problems down the road. If it works i will try to backup and go to latest android 9, since many are complaining about version 10 with emmc apparently forgotten.
Also unfortunately i lost twrp, and don't have a sd cardfor flashing,and wouldn't like to wipe data to install twrp.
I thought about it and my only course of action is getting the boot.img, dd is out of option since I am not rot, is there a non root way to unpack if it turns out 10.0.13 causes a bootloop?
Sorry if some things don't make sense I am getting back to this after a long hiatus, can I still extract the img. from zip, or do I have to upack it with python?
Thank you.
Click to expand...
Click to collapse
It was a minor/small update, I doubt it causes a bootloop.
You can flash Orange Fox through fastboot, no need to wipe data and from there either just flash Magisk or backup your boot and patch it if you prefer this method.
Not sure to which image you refer, no need to unpack the image by any method.
SubwayChamp said:
It was a minor/small update, I doubt it causes a bootloop.
You can flash Orange Fox through fastboot, no need to wipe data and from there either just flash Magisk or backup your boot and patch it if you prefer this method.
Not sure to which image you refer, no need to unpack the image by any method.
Click to expand...
Click to collapse
Thank you again, for orange fox especially,
I thought I needed Payload dumper, or is that only after android 10?
Thanks for the help, i only liked your replies, i dont know if they removed thanks globally or only on QA forums
Ikarus01 said:
Thank you again, for orange fox especially,
I thought I needed Payload dumper, or is that only after android 10?
Click to expand...
Click to collapse
No, if you refer to a method to unpack the ROM it comes either in zip format (recovery) or in tar.gz format (fastboot), you just need to unpack it with something like Winrar other 7zip and inside you will find the boot image.
It's a global change, in this new platform they removed the thanks option, I disagree but this is how it is.
SubwayChamp said:
No, if you refer to a method to unpack the ROM it comes either in zip format (recovery) or in tar.gz format (fastboot), you just need to unpack it with something like Winrar other 7zip and inside you will find the boot image.
Click to expand...
Click to collapse
Oh that is good to hear!
Thank You again you really helped me here.
Sadly I can only like your post, I guess that is the new rep system?
Have a good day!
Cheers