Related
ADDING THE LINK HERE NOW : https://www.dropbox.com/s/it4ji9mlohfgagf/NexusOne-rescue-tools.zip
And please, a THANKS would be great if this helped you.
For some reason the phone one day just didn't boot. Was stuck on X logo.
We have tried alot... can't get into recovery, so flashed custom recovery, both RA and CWM... can't get into any of them, just stuck on X.
The phone was stock, and unrooted.
We managed to unlock bootloader via fastboot and root it.
Tried the PASSIMG.ZIP method - not working.
Any ideas?
.... please? =(
EDIT: Problem solved! Send me a PM if you're in the same seat, and i could send you all the files you need.
Oh, all you need is your FASTBOOT to work, no need for ADB, since it didn't work for me either.
EDIT #2:
The reason is that i have a file (ADB, and all the *.img's) needed on my server, and don't wanna post the link here so that's why i have done it thru PM.
But i'll update the first post and just delete the link, so when anyone needs it they can PM me.
So far (2012-02-10) 14 phones confirmed back up running, including mine. Got 2 unconfirmed, and just sent 5 PM's to guys with the same problem.
*** PM ME FOR THE LINK TO THE *.ZIP ***
Unzip, open an command promt, and:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash radio radio.img
fastboot flash system system.img
do the commands in that order, and when you are done reboot the phone
and see if it boots.
if NOT: keep on flashing ONLY the boot.img again and again until it
boots. it seems like the boot partition is corrupted and may need alot
of flashing until it works.
i think i flashed like 100 times before it booted. =)
There is also another recovery in that zip... RA's recovery. You can also try that one, no harm done!
Once you get it to boot, you will have FroYo 2.2 installed.
If you got it to boot with recovery.img just let android update to latest (2.3.7?)
If you have RA's recovery, just flash back recovery.img or you wont be able to upgrade to 2.3.7 "the stock way"
Can you boot without sd card?
Maybe Hardware--
rugmankc said:
Can you boot without sd card?
Maybe Hardware--
Click to expand...
Click to collapse
Sorry, no. Not booting when i remove sdcard either.
:/
May be hardware
rugmankc said:
May be hardware
Click to expand...
Click to collapse
How do i find out?
When we searched yesterday (google), we found some ppl who had fixed it, now i can't find those pages again..
So anyone here who knows what to try?
I've been in a similar situation before and just kept fastboot flashing system, recovery, and boot, and eventually I recovered the phone...
I assume since you mentioned that you unlocked the bootloader, that you can get into fastboot? If so, flash a custom recovery (I'd recommend CWM since it includes an option to wipe the system partition) and boot into it.
Code:
fastboot flash recovery "c:\location\to\recovery.img
fastboot boot recovery "c:\location\to\recovery.img
If you can get that far, wipe your /system partition and do a factory reset. Then install CM7 (or whatever ROM you want) and gapps.
bassmadrigal said:
I assume since you mentioned that you unlocked the bootloader, that you can get into fastboot? If so, flash a custom recovery (I'd recommend CWM since it includes an option to wipe the system partition) and boot into it.
Code:
fastboot flash recovery "c:\location\to\recovery.img
fastboot boot recovery "c:\location\to\recovery.img
If you can get that far, wipe your /system partition and do a factory reset. Then install CM7 (or whatever ROM you want) and gapps.
Click to expand...
Click to collapse
Thanks!
But we have tried to fastboot system.img, boot.img and recovery.img
Still stuck on X.
Is that code any different perhaps?
I can't try that now, that's why i ask instead of try it =)
All the commands that I posted are supposed to do is install a custom recovery and then boot into it. From recovery, you need to wipe your device by wiping the /system partition and doing a Factory Reset/Data Wipe. Then install whatever ROM you want to.
I've never tried using fastboot to install the system image, so I can't comment on that at all.
O M G!!!
i actually got the phone up and running!! everything is working now, i'm just too awesome
If anyone is interested, i could find out what i did, and which files i flashed, etc etc.
Just an update:
(mostly to bump this)
3 more ppl who had the same problem has now got this fixed
Woa, check your PM
Check you inbox buddy! Tack på förhand
mrBira said:
Just an update:
(mostly to bump this)
3 more ppl who had the same problem has now got this fixed
Click to expand...
Click to collapse
Is it an illegal method, or is there another reason why a fix like this you're only sharing by PM instead of posting it here? I sent you a PM over 24hrs ago and haven't heard back yet. I would think making one helpful post would be much easier than getting irritated at replying to each of 10-100+ PMs
NismoDrift240 said:
Is it an illegal method, or is there another reason why a fix like this you're only sharing by PM instead of posting it here? I sent you a PM over 24hrs ago and haven't heard back yet. I would think making one helpful post would be much easier than getting irritated at replying to each of 10-100+ PMs
Click to expand...
Click to collapse
HEHEH... illegal
No, ofc not (is there any way to fix a phone that's not legal?).
The reason is that i have a file (ADB, and all the *.img's) needed on my server, and don't wanna post the link here so that's why i have done it thru PM.
But i'll update the first post and just delete the link, so when anyone needs it they can PM me.
So far 14 phones confirmed back up running, including mine. Got 2 unconfirmed, and just sent 5 PM's to guys with the same problem.
mrBira said:
HEHEH... illegal
No, ofc not (is there any way to fix a phone that's not legal?).
The reason is that i have a file (ADB, and all the *.img's) needed on my server, and don't wanna post the link here so that's why i have done it thru PM.
But i'll update the first post and just delete the link, so when anyone needs it they can PM me.
So far 14 phones confirmed back up running, including mine. Got 2 unconfirmed, and just sent 5 PM's to guys with the same problem.
Click to expand...
Click to collapse
That makes perfect sense, I'm the same way. Thanks for getting back to me, here's to hoping I make 15...
same prob.
I sent you a PM, bro. Get back to me as soon as you can! Thanks!
Nexus One recovery boot error
PM sent. Thank you for your assistance.
i would like to know how to you solve the problem
No recovery for unrooted fones
first root ur phone using passimg.img
and fastboot flash bootloard oem unlock etc
and then try to flash a recovery using
fastboot flash recovery recovery.img
then u r done
Thank if it helps u
Hello,
I cannot make sense of either the written directions or the Youtube video. They assume knowledge that I do not possess. Speaking of which...
In the "flash a recovery" step, is this supposed create a recovery image of some sort, or flash an already existing one onto the phone. If the latter, where does this recovery image come from?
In the kernel step, it says to place your kernel in the /Data/Kernel directory. How am I supposed to obtain the kernel image?
Thank you in advance.
(I posted this here because I do not have the necessary permissions to reply to Hansoon2000's thread)
psterrett said:
Hello,
I cannot make sense of either the written directions or the Youtube video. They assume knowledge that I do not possess. Speaking of which...
In the "flash a recovery" step, is this supposed create a recovery image of some sort, or flash an already existing one onto the phone. If the latter, where does this recovery image come from?
In the kernel step, it says to place your kernel in the /Data/Kernel directory. How am I supposed to obtain the kernel image?
Thank you in advance.
(I posted this here because I do not have the necessary permissions to reply to Hansoon2000's thread)
Click to expand...
Click to collapse
Assuming you are S-on you dont have to flash a kernel if you are just rooting it
Root your phone, S-off it(If you want to... I recommend it), and just flash a rom via recovery
I believe the recovery is in the folders already? Can anyone confirm?
bilibox said:
Assuming you are S-on you dont have to flash a kernel if you are just rooting it
Root your phone, S-off it(If you want to... I recommend it), and just flash a rom via recovery
I believe the recovery is in the folders already? Can anyone confirm?
Click to expand...
Click to collapse
Correct CW or WCX just have to choose which you want
It's pretty straight forward and noob friendly...follow instructions to unlock bootloader, choose cwm or wcx recovery then press button to flash...kernel is optional, if you want one download one from here and put it in the kernels subfolder...
Everything comes from/is located in the data folder and its sub-directories you also extracted
Sent from my HTC PH39100 using xda app-developers app
Thank you
Thanks for the replies. I found a simpler to follow method, using fastboot.exe and an included recovery image, and successfully rooted the phone.
Now, I'm going to do some RTFMing, so this won't be an issue again.
One piece of information that might help you is understanding that the term "recovery" can mean two things. In the context of "flashing a recovery" in the process of rooting your phone, what this means is flashing a recovery tool to the recovery partition of your phone. Your phone has a special place set aside for a backup OS (or recovery tool) in case things go south for your actual OS. The recovery you can flash with the all-in-one tool will install CWM (ClockWorkMod), or WCX. Personally, I use CWM. By holding the power key and volume down when you start your phone, you gain access to the boot menu, where you can load the recovery tool. This allows you to do all sorts of powerful things, from flashing kernels and ROMS, to preforming backups and restores, to clearing caches, and all sorts of other power-user type functions.
Hope that helps, and glad you got your phone rooted. These things are a lot of fun once you open them up a little
Ok, i was looking for flashing a kernel on an Lg Optimus black (i do not own the device), but i really can't fins anything... Can someone be gentle with me and explain how to plug the device in fastboot mode and flash the kernel.... I work with the Xperia devices and there the life is easier xD. So the questions are:
1)Where can i find the drivers USB?
2)How to plug the device in fastboot mode??
3)How to unlock bootloader
and i think that when i achived those passages i know how to go on... maybe like this:
1- Enter in the folder with fastboot's files inside
2- press shift + right-click and then select open command prompt here
3- Type: fastboot flash boot boot.img
am i wrong?? Please tell all the things that can be helpfull, but only for me, maybe for others noobs like me that dosen't know anything about this device this post i think the can be very helpfull for lots of people. :laugh:
Thank you guys and for your time
p.s.: Sorry, for bad english
Enri1196 said:
Ok, i was looking for flashing a kernel on an Lg Optimus black (i do not own the device), but i really can't fins anything... Can someone be gentle with me and explain how to plug the device in fastboot mode and flash the kernel.... I work with the Xperia devices and there the life is easier xD. So the questions are:
1)Where can i find the drivers USB?
2)How to plug the device in fastboot mode??
3)How to unlock bootloader
and i think that when i achived those passages i know how to go on... maybe like this:
1- Enter in the folder with fastboot's files inside
2- press shift + right-click and then select open command prompt here
3- Type: fastboot flash boot boot.img
am i wrong?? Please tell all the things that can be helpfull, but only for me, maybe for others noobs like me that dosen't know anything about this device this post i think the can be very helpfull for lots of people. :laugh:
Thank you guys and for your time
p.s.: Sorry, for bad english
Click to expand...
Click to collapse
You can google these questions too..
Sent from my A2 using xda app-developers app
NC4777 said:
You can google these questions too..
Click to expand...
Click to collapse
but i can't find it out!!! plz if someone else have to answer like this plz stay away... Man please if it was a joke this wasn't funny i really don't know how to flash a new f*****g kernel, to flash cm10.1 nightly
The Optimus Black doesn't use fastboot. Everything is done through recovery.
Download Clockwork Mod from the Play store, use that app to flash a custom recovery.
Enter recovery by repeatedly pressing volume down at power up or use a reboot to recovery app.
To flash roms/kernels, copy to your sd card, boot into recovery, select install zip.
The bootloader is not locked, unless you have flashed the offical LG ICS rom with the smartflash tool. If you have and want to unlock it, just flash any froyo/gingerbread offical LG rom with smartflash, that will unlock.
1. Make sure you are rooted, if not, read Nooby's how-to on how to do it. It's a sticky in LGP970 section on xda.
2. Once rooted, you can install ROM Manager and flash cwm/twrp recovery from there. Give it root permissions when asked for.
3. Boot into recovery using ROM Manager or any other third-party app. Flash the .zip for the kernel you want. Make sure it is compatible with the ROM you are using.
4. Once kernel flashed, boot into the system.
Bootloader is generally unlocked unless you are running official ICS on your OB. If that is the case, don't do any of the above mentioned steps as you will end in a boot loop.
If on official ICS, use Smart Flash Tool to flash unlocked bootloader. You can follow instructions here on jockjoint's thread
Once bootloader is unlocked and you have flashed su.zip as per instructions in the previouslsy mentioned thread, boot into recovery (it's already there in the unlocked bootloader flash).
Once in there, flash a compatible kernel and ROM as per your needs/liking.
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
Noob here in flashing in partitions
I recently brought mi a2
I unlocked bootloader and critical also
Flashed magisk modified boot
I want to flash twrp
I can boot into temp twrp but when I try to start sideload it gets stuck at 0%
When I try to flash from internal it shows in text which is not readable
Anyhow can help how can I flash permanent twrp and custom rom
No one is answering... Even i want to know how to flash twrp... Everything is so confusing in this forum. Other device it's very easy
poran123 said:
No one is answering... Even i want to know how to flash twrp... Everything is so confusing in this forum. Other device it's very easy
Click to expand...
Click to collapse
Your memory is crypted, you have to decrypt it first. Or side load twrp 3.3.1.-3. You have tutorial here on xda, just folow it: https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Im sending you pm link for 3.3.1.-3 twrp