Creating modified boot.img and enabling adb during first boot. - Xiaomi Redmi Note 3 Guides, News, & Discussion

Creating modified boot.img and enabling adb during first boot. - Xiaomi Redmi Note 3 Guides, News, & Discussion

Modified boot.img of a rom is required to be flashed on that rom so that it works with TWRP.
Enabling ADB during first boot creates a way out in case your phone bootloops or stuck at MI logo and also hardbricked.
Many people hardbricked their phone while flashing MIUI based roms through TWRP, and they had to test-point to bring their phone back to life, my mod enables adb during boot and so people who used my mod and hardbricked their phone can access adb when their phone is stuck at MI logo or bootlooping and thus revive their phone.
Tools needed:-
1)Notepad++ (google it and download)
2)Android Image Kitchen(AIK) http://forum.xda-developers.com/attachment.php?attachmentid=3638835&d=1454959265
Steps:-
1)Download the required rom and extract its boot.img
2)Copy the boot.img to AIK folder and drag boot.img and drop it on unpackimg.bat
3)Open ramdisk folder and look for default.prop , open them with Notepad++
4)Editing default.prop Note:- This will enable adb at first boot
5)Change
Code:
ro.secure=1 to ro.secure=0
ro.adb.secure=1 to ro.adb.secure=0
ro.debuggable=0 to ro.debuggable=1
persist.sys.usb.config=none to persist.sys.usb.config=adb
delete the line ro.secureboot.devicelock=1 if present
OR (Alternate way)(recommended)
open ramdisk and look for fstab.qcom, open with notepad++ and search for ",verify" (without quotes) and delete it and save.
6)Now execute repackimg.bat, a image-new.img file will be compiled.
7)Flash the image-new.img through TWRP or through fastboot using "Fastboot flash boot image-new.img"
That's all
P.S:- Remember only use Boot.img specific for the miui version you wanna run, boot.img version not matching with MIUI version
will cause the Wifi to stop working.
Press thanks If this helped.:good:
Any queries feel free to ask me.:laugh:

Does the modified boot.img procedure need to be done for every ROM or just for the MIUI ROMs? I want to install the AOSP ROM and later CM 13 but I'm still not sure about the whole flashing process.
Sent from my Redmi Note 3 using XDA-Developers mobile app

SkinCoffin said:
Does the modified boot.img procedure need to be done for every ROM or just for the MIUI ROMs? I want to install the AOSP ROM and later CM 13 but I'm still not sure about the whole flashing process.
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
modified boot.img is only for official MIUI roms, all other roms doesnt need it

Rajdip said:
modified boot.img is only for official MIUI roms, all other roms doesnt need it
Click to expand...
Click to collapse
So if I'm on Miui Official Global ROM 7.2.3 all I have to do is flash TWRP through fastboot, boot into it and flash the new ROM+GApps through it?

SkinCoffin said:
So if I'm on Miui Official Global ROM 7.2.3 all I have to do is flash TWRP through fastboot, boot into it and flash the new ROM+GApps through it?
Click to expand...
Click to collapse
exactly

Rajdip said:
exactly
Click to expand...
Click to collapse
Thank you! I just did it. It has booted and almost over in the "Optimizing apps" window. Thing is, I did forget to wipe system, data and cache before flashing, should I do it again or will it be fine like this?
EDIT: I rebooted the phone into recovery, wiped system, data and cache, flashed the ROM zip and wiped cache and dalvik cache. I booted the phone and it showed the Mi logo, then 4 circles screen flying around (green, red, blue and yellow) and it has been like this for like 5 min now.. Did I do something wrong? I'm starting to worry to be honest.

SkinCoffin said:
Thank you! I just did it. It has booted and almost over in the "Optimizing apps" window. Thing is, I did forget to wipe system, data and cache before flashing, should I do it again or will it be fine like this?
EDIT: I rebooted the phone into recovery, wiped system, data and cache, flashed the ROM zip and wiped cache and dalvik cache. I booted the phone and it showed the Mi logo, then 4 circles screen flying around (green, red, blue and yellow) and it has been like this for like 5 min now.. Did I do something wrong? I'm starting to worry to be honest.
Click to expand...
Click to collapse
it takes time to boot for the first time, did it boot now?

Rajdip said:
it takes time to boot for the first time, did it boot now?
Click to expand...
Click to collapse
Still hasn't booted. It has been on the flying circles screen for around 10 minutes now. Maybe fastboot twrp again and do the process all over again?

SkinCoffin said:
Still hasn't booted. It has been on the flying circles screen for around 10 minutes now. Maybe fastboot twrp again and do the process all over again?
Click to expand...
Click to collapse
Try again, goto TWRP, wipe system,data,cache,dalvik and flash the rom. Now reboot...

Rajdip said:
Try again, goto TWRP, wipe system,data,cache,dalvik and flash the rom. Now reboot...
Click to expand...
Click to collapse
So I shouldn't reinstall TWRP through fastboot?
EDIT: Ok so I restarted the phone and it booted normally into the ROM, everything seems alright. Will check if I have any problem, if I do I'll just reflash it.

SkinCoffin said:
So I shouldn't reinstall TWRP through fastboot?
Click to expand...
Click to collapse
No, first try what I said, dont wipe cache and dalvik after the rom is flashed

Rajdip said:
No, first try what I said, dont wipe cache and dalvik after the rom is flashed
Click to expand...
Click to collapse
Ok so I restarted the phone and it booted normally into the ROM, everything seems alright. Will check if I have any problem, if I do I'll just reflash it.

SkinCoffin said:
Ok so I restarted the phone and it booted normally into the ROM, everything seems alright. Will check if I have any problem, if I do I'll just reflash it.
Click to expand...
Click to collapse
okay

i do exactly like your tutor...i edit boot.img n delete ",verify"
repack than delete original boot.img, than use moded boot.img... but wifi doesn't work...
where my mistake...?

Mayoz said:
i do exactly like your tutor...i edit boot.img n delete ",verify"
repack than delete original boot.img, than use moded boot.img... but wifi doesn't work...
where my mistake...?
Click to expand...
Click to collapse
are you sure you are using the boot.img of the MIUI version you are flashing? there is two 7.2.3.0 version of boot.img one for global and one for china. Anyway try this and see if wifi works, goto TWRP(I hope you've already deleted the emmc_appsboot file), select mount and then tick on mount system as read only. Then flash the rom. This method will replace TWRP with MIUI recovery but your wifi should start working.

Rajdip said:
are you sure you are using the boot.img of the MIUI version you are flashing? there is two 7.2.3.0 version of boot.img one for global and one for china. Anyway try this and see if wifi works, goto TWRP(I hope you've already deleted the emmc_appsboot file), select mount and then tick on mount system as read only. Then flash the rom. This method will replace TWRP with MIUI recovery but your wifi should start working.
Click to expand...
Click to collapse
yes using the boot.img of the MIUI version to flashing...from recovery rom stable 7.2.3.0 china....maybe my mistake i replace emmc_appsboot file from miui forum...not delete "will replace TWRP with MIUI recovery...' still can booting? i already UBL...

Mayoz said:
yes using the boot.img of the MIUI version to flashing...from recovery rom stable 7.2.3.0 china....maybe my mistake i replace emmc_appsboot file from miui forum...not delete "will replace TWRP with MIUI recovery...' still can booting? i already UBL...
Click to expand...
Click to collapse
I didnt get you, can you be more clear?

Do I need to use Windows 64bits to flash TWRP?
Thanks.

pepemonje said:
Do I need to use Windows 64bits to flash TWRP?
Thanks.
Click to expand...
Click to collapse
no need 32bit works

Hello, I've followed a certain tutorial and flashed a fastboot Rom with modified emmc file in attempt to unlock bootloader by force because, even after two weeks of trying, I can't get a confirmation SMS from xiaomi to confirm sending an unlock request. After doing it and flashing TWRP onto my device, I'm still unable to enter recovery. Just shows a picture of device and a disconnected usb cable. I need to flash SuperSU in order to get root access.
Because this device is getting me really confused, please answer a couple of questions for me.
If I flash a recently uploaded global stable ROM 7.2.3.0. and flash TWRP with a modified boot image from this tutorial, will I finally be able to enter recovery and install SuperSU?
Flashing will probably relock my bootloader. Is it possible for me to finally enter TWRP and flash SuperSU after flashing the new boot image?
I've thought that I could enter TWRP just by unlocking the bootloader but it seems that I've missed something. I can't remember last time a phone got me this confused.
My only goal here is being able to enter TWRP and rooting my phone, I gave up on unlocking the bootloader officially because I can't ever get that confirmation SMS.
I appreciate the help!! :fingers-crossed:

Related

Status 7

I couldnt find any fix or helpful answers elsewhere on the web
Many of you are aware of the status 7 installation abort when trying to install a new rom
Ive been tinkering since last night trying to get miui 2.10.12 on my nexus 7 and every time I get a "Installation Abort (Status 7)
how do I get it to finish installation?
ive tried with multiple roms, CM10, MIUI, Kang all have same result
I have clockwork mod installed, from rom manager
I made sure I wipe data and cache and also davlik cache
any suggestions?
and i thank everyone in advance

I think you will hopefully get more joy posting in the Q&A section.
I have read that it can be fixed by fastbooting stock and then re-rooting though. If you can make backups first, you should, because this will wipe everything.

z1gackly said:
I think you will hopefully get more joy posting in the Q&A section.
I have read that it can be fixed by fastbooting stock and then re-rooting though. If you can make backups first, you should, because this will wipe everything.
Click to expand...
Click to collapse
what ive been doing is not making any backups (nothing important to save) and just using nexus toolkit to flash back stock and starting over and trying new way every time
still nothing though after about the 20th time

No idea then sorry. Stick with rooted stock?

z1gackly said:
No idea then sorry. Stick with rooted stock?
Click to expand...
Click to collapse
i think I might have to, ive never had any issues with custom roms (to speak of)
oh well, at least im happy with stock, i just love miui.
anyone else have answers please chip in, i give thanks!

harecurtis said:
I couldnt find any fix or helpful answers elsewhere on the web
Many of you are aware of the status 7 installation abort when trying to install a new rom
Ive been tinkering since last night trying to get miui 2.10.12 on my nexus 7 and every time I get a "Installation Abort (Status 7)
how do I get it to finish installation?
ive tried with multiple roms, CM10, MIUI, Kang all have same result
I have clockwork mod installed, from rom manager
I made sure I wipe data and cache and also davlik cache
any suggestions?
and i thank everyone in advance
Click to expand...
Click to collapse
You're using a wrong recovery. Install TWRP recovery using Goo Manager. Get it from Google Play Store

joedoe said:
You're using a wrong recovery. Install TWRP recovery using Goo Manager. Get it from Google Play Store
Click to expand...
Click to collapse
give me 5 minutes, while i try your method.

harecurtis said:
give me 5 minutes, while i try your method.
Click to expand...
Click to collapse
joedoe said:
You're using a wrong recovery. Install TWRP recovery using Goo Manager. Get it from Google Play Store
Click to expand...
Click to collapse
its a no go

anyone else wanna help me?
ive tried almost everything:/

download TWRP for the Nexus 7 (grouper) Here : http://teamw.in/project/twrp2/103
Since your rooted you can use a simple app to flash the Image. Download and install the free app here http://forum.xda-developers.com/showthread.php?t=1790150&highlight=flash+gui
Open the free app and select the option for Recovery Image. Hit Browse and find the recovery image you downloaded and select it.Once finished hit flash image. It will ask you to confirm this image is a recovery image. Hit yes and it'll flash.
Then reboot to recovery, you can do this by using Terminal Emulator from the market issue this command
Code:
su *hit enter*
adb reboot recovery
If that doesnt work.. remove "adb" I forget if you need it or not :S
This should put you into TWRP Recovery.. go ahead and flash your ROM. Make sure you follow the proper procedure. I recommend this
1.Wipe data/Factory Reset
2. Wipe Cache Partition
3.Wipe Dalvik Cache
4. Format /System
then proceed to flash the ROM and Gapps. and Reboot.

ÜBER™ said:
download TWRP for the Nexus 7 (grouper) Here : http://teamw.in/project/twrp2/103
Since your rooted you can use a simple app to flash the Image. Download and install the free app here http://forum.xda-developers.com/showthread.php?t=1790150&highlight=flash+gui
Open the free app and select the option for Recovery Image. Hit Browse and find the recovery image you downloaded and select it.Once finished hit flash image. It will ask you to confirm this image is a recovery image. Hit yes and it'll flash.
Then reboot to recovery, you can do this by using Terminal Emulator from the market issue this command
Code:
su *hit enter*
adb reboot recovery
If that doesnt work.. remove "adb" I forget if you need it or not :S
This should put you into TWRP Recovery.. go ahead and flash your ROM. Make sure you follow the proper procedure. I recommend this
1.Wipe data/Factory Reset
2. Wipe Cache Partition
3.Wipe Dalvik Cache
4. Format /System
then proceed to flash the ROM and Gapps. and Reboot.
Click to expand...
Click to collapse
ill try this in just a few minutes as im flashing stock as we speak and "starting fresh"

harecurtis said:
ill try this in just a few minutes as im flashing stock as we speak and "starting fresh"
Click to expand...
Click to collapse
If you're going that route.. you might as well just use fastboot to reflash recovery instead of the app.
Download the same image i linked to earily. While in the bootloader issue this command
Code:
fastboot flash recovery name-of-recovery.img
Make sure you have the Command Prompt in the same directory as the recovery image.
So say its in your downloads folder on your computer open CMD and cd to that directory.
Code:
cd C:\Users\Name\Downloads
Or just open yoru downloads folder and Shift + Right click and select "open command window here" then issue the fastboot command.

ÜBER™ said:
download TWRP for the Nexus 7 (grouper) Here : http://teamw.in/project/twrp2/103
Since your rooted you can use a simple app to flash the Image. Download and install the free app here http://forum.xda-developers.com/showthread.php?t=1790150&highlight=flash+gui
Open the free app and select the option for Recovery Image. Hit Browse and find the recovery image you downloaded and select it.Once finished hit flash image. It will ask you to confirm this image is a recovery image. Hit yes and it'll flash.
Then reboot to recovery, you can do this by using Terminal Emulator from the market issue this command
Code:
su *hit enter*
adb reboot recovery
If that doesnt work.. remove "adb" I forget if you need it or not :S
This should put you into TWRP Recovery.. go ahead and flash your ROM. Make sure you follow the proper procedure. I recommend this
1.Wipe data/Factory Reset
2. Wipe Cache Partition
3.Wipe Dalvik Cache
4. Format /System
then proceed to flash the ROM and Gapps. and Reboot.
Click to expand...
Click to collapse
didnt work(

harecurtis said:
didnt work(
Click to expand...
Click to collapse
?? Is your bootloader unlocked? You are rooted still correct? I dont see how your even rooting if you dont flash a Superuser package with recovery??

ÜBER™ said:
?? Is your bootloader unlocked? You are rooted still correct? I dont see how your even rooting if you dont flash a Superuser package with recovery??
Click to expand...
Click to collapse
yes my bootloader is unlocked, and I rooted as well
what Im using is wugfresh nexus root toolkit 1.5.3

harecurtis said:
yes my bootloader is unlocked, and I rooted as well
what Im using is wugfresh nexus root toolkit 1.5.3
Click to expand...
Click to collapse
Stop... dont use that.. -_-. Do it manually..

ÜBER™ said:
Stop... dont use that.. -_-. Do it manually..
Click to expand...
Click to collapse
okay, can you send me a lint to a post that I can manually do it?
and thanks so much!

harecurtis said:
okay, can you send me a lint to a post that I can manually do it?
and thanks so much!
Click to expand...
Click to collapse
Ill write you up a quick tutorial.
First download this zip it contains adb and its .dll's needed to be executed and fastboot.exe for flashing
http://db.tt/EOwGUAPV
Unzip it and put that TWRP image in the same folder.
Then in that folder Shift + Right click and select open command prompt here.
Then type
Code:
adb reboot bootloader
This will boot you into the bootloader. Once in the bootloader do this command
Code:
fastboot flash recovery name-of-recovery.img
Hopefully your smart enough to realize that means type in the name of the recovery not exactly what that says.. for instance openrecovery-twrp... etc etc.
Then once its finished writing the recovery hit the volume up until the "Start" Says Recovery Mode. Then hit the power button. You should now be booting in the TWRP. Then flash your ROM.

ÜBER™ said:
Ill write you up a quick tutorial.
First download this zip it contains adb and its .dll's needed to be executed and fastboot.exe for flashing
http://db.tt/EOwGUAPV
Unzip it and put that TWRP image in the same folder.
Then in that folder Shift + Right click and select open command prompt here.
Then type
Code:
adb reboot bootloader
This will boot you into the bootloader. Once in the bootloader do this command
Code:
fastboot flash recovery name-of-recovery.img
Hopefully your smart enough to realize that means type in the name of the recovery not exactly what that says.. for instance openrecovery-twrp... etc etc.
Then once its finished writing the recovery hit the volume up until the "Start" Says Recovery Mode. Then hit the power button. You should now be booting in the TWRP. Then flash your ROM.
Click to expand...
Click to collapse
thanks
ill do that in a few minutes, im in the middle of trying another process, and if it fails ill try your method.
and should i re lock my bootloader before i try your method, or can i just keep it unlocked?

harecurtis said:
thanks
ill do that in a few minutes, im in the middle of trying another process, and if it fails ill try your method.
and should i re lock my bootloader before i try your method, or can i just keep it unlocked?
Click to expand...
Click to collapse
Keep it unlocked.... otherwise you'll have to re unlock it...

Flashing Boot.img doesn't boot the phone

Hey folks
Tried to flash this boot.img from
http://forum.xda-developers.com/showthread.php?t=2018822&highlight=boot+img
to flash JB ROM and it has stucked on 'Free Xperia' logo when turning on. Had to flash stock kernel back. This .img is necessary for flashing the rom according to steps manual.
Any help please why this could happen?
Cheers!

Look for a more stable ROM that ROM is still in the Alpha stages. There are many on here
Sent from my Xperia Arc S using xda app-developers app

leeris said:
Any help please why this could happen?
Click to expand...
Click to collapse
...
First time installing CyanogenMod 10.1 to Arc/S another ROM:
- Make sure you're running bootloaders unlocked
-Flash the Boot.img provided (Don't flash other boot.img because is different)
- Copy GApps and CM10.1 ZIPs to your internal SDCard
- Boot into Recovery
- Flash CM10.1 zip from internal SDCard
- Flash GApps zip from internal SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Click to expand...
Click to collapse

XperienceD said:
...
Click to expand...
Click to collapse
Thanks, that's what I did. But the second step was unsuccessful...
-Flash the Boot.img provided (Don't flash other boot.img because is different)
I flashed the image and the phone didn't boot up, stucked on the logo...

leeris said:
Thanks, that's what I did. But the second step was unsuccessful...
-Flash the Boot.img provided (Don't flash other boot.img because is different)
I flashed the image and the phone didn't boot up, stucked on the logo...
Click to expand...
Click to collapse
Try in this order, flash the kernel, reboot into CMW, wipe cache, data and battery, install ROM, reboot, flash gapps and reboot again.

thanks. my question is, how do I reboot into CWM, when after flashing the kernel, my phone is stucked on the logo? I must be missing something...

leeris said:
thanks. my question is, how do I reboot into CWM, when after flashing the kernel, my phone is stucked on the logo? I must be missing something...
Click to expand...
Click to collapse
I thought I had the same problem, but all u need to do is wait. It stays on the fxp screen for ages, maybe 30 seconds once it lights up then start pressing vol down to get into recovery.
Sent from my Xperia Arc S using xda app-developers app

leeris said:
thanks. my question is, how do I reboot into CWM, when after flashing the kernel, my phone is stucked on the logo? I must be missing something...
Click to expand...
Click to collapse
To enter CWM, you need to press the power button, when phone vibrates, press Volume Down button many times until a Recovery menu appears.
Only possible if you have custom kernel installed (if it has one).

Root N Dev Preview 5

Can anyone here point in the right direction to guide me through DP5 root? TWRP hangs on splash screen when attempting to install. Thanks!
Sent from my Nexus 6P using XDA-Developers mobile app

TWRP can't decrypt the N system right now. So it will stay stuck on the splash screen.
The most common way around here, is to decrypt your device's storage. Once, you have decrypted, you will be able to access the recovery, and flash the latest SuperSU zip for root.

DJBhardwaj said:
TWRP can't decrypt the N system right now. So it will stay stuck on the splash screen.
The most common way around here, is to decrypt your device's storage. Once, you have decrypted, you will be able to access the recovery, and flash the latest SuperSU zip for root.
Click to expand...
Click to collapse
Thanks! What's the best way of doing that!?

DLloyd said:
Thanks! What's the best way of doing that!?
Click to expand...
Click to collapse
Be advised that decrypting will wipe off your complete data, including that on the internal storage. So, backup first.
The first step would be to download the modified boot image for DP5: http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684 (Make sure that you download the correct file).
Next, reboot your device into bootloader mode and flash the boot image using the following command:
Code:
fastboot flash boot boot.img
Once that is done, you will need to decrypt using the following command (Do not mix "fastboot erase" command with "fastboot format"):
Code:
fastboot format userdata
Finally, reboot your device. Now, you will be able to access TWRP and flash SuperSU: http://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip

This is great but unfortunately no joy - I'm still stuck on the TWRP splash screen when trying to enter recovery, after flashing the modified boot.img - in security it still show's encrypted?

DLloyd said:
This is great but unfortunately no joy - I'm still stuck on the TWRP splash screen when trying to enter recovery, after flashing the modified boot.img
Click to expand...
Click to collapse
Have you formatted the userdata after flashing the boot.img?

DJBhardwaj said:
Have you formatted the userdata after flashing the boot.img?
Click to expand...
Click to collapse
Yeah, exactly as advised... re-downloaded boot.img to try again, no luck

DLloyd said:
Yeah, exactly as advised... re-downloaded boot.img to try again, no luck
Click to expand...
Click to collapse
Go to Settings > Security and see if Encrypt phone option is available or greyed out. Also try reflashing TWRP.

DJBhardwaj said:
Go to Settings > Security and see if Encrypt phone option is available or greyed out. Also try reflashing TWRP.
Click to expand...
Click to collapse
It show's Encrypted, with no option to change, have tried re-flashing TWRP but nothing. How do I make sure format userdata has worked correctly? Appreciate your help!

DLloyd said:
It show's Encrypted, with no option to change, have tried re-flashing TWRP but nothing
Click to expand...
Click to collapse
Then the decryption process didn't work at all.
Download this specific boot.img: https://www.androidfilehost.com/?fid=24591023225178833
Flash it via fastboot. And then, "fastboot format userdata" and "fastboot format cache".
Finally, reboot.

DJBhardwaj said:
Then the decryption process didn't work at all.
Download this specific boot.img: https://www.androidfilehost.com/?fid=24591023225178833
Flash it via fastboot. And then, "fastboot format userdata" and "fastboot format cache".
Finally, reboot.
Click to expand...
Click to collapse
Yeah, still no joy... I'll revert to previous dev preview for root. Thanks anyway!

DLloyd said:
Yeah, still no joy... I'll revert to previous dev preview for root. Thanks anyway!
Click to expand...
Click to collapse
I rooted my Nexus 6P successfully with that specific boot.img and flash TWRP for many times.
1.flash specific boot.img
2.flash TWRP 3.0.0.0
3.get into TWRP-Wipe-format data and type "yes"
4.reboot to bootloader, flash TWRP 3.0.0.0 again.
5.get into TWRP and flash supersu
6.do not reboot or clean cache, get into wipe, and format data
7.reboot to bootloader, flash TWRP 3.0.2.0
7.get into TWRP and flash supersu
8.done
Since it seems ridiculous, it works.

DLloyd said:
Yeah, still no joy... I'll revert to previous dev preview for root. Thanks anyway!
Click to expand...
Click to collapse
Weird. I have followed the same drill about 2-3 times on DP5, and it works perfectly.

using CF Auto root works with Android N DP5. Don't need custom recovery.

XRaptor29 said:
using CF Auto root works with Android N DP5. Don't need custom recovery.
Click to expand...
Click to collapse
How did you pull that off, I recently did that and it bootloop on the cf auto root screen

jussaren said:
How did you pull that off, I recently did that and it bootloop on the cf auto root screen
Click to expand...
Click to collapse
Make sure boot loader is unlocked. I never had the CF Auto Root screen boot loop, it does boot loop a few times when booting afterwards but that's it finishing it up.
Last night I unencrypted my phone and twrp works fully so I could flash a custom kernel. It's sad that NP5 forces encryption and you have to flash the stock kernel with encryption disabled to unencrypted. I can provide a link if you're interested in that. It provides the kernel and step by step process.
Edit: didn't realize that one guy with the Droid Origin signature had the link also, I Googled and found it but this is how I unencrypted and everything last night. http://www.droidorigin.com/decrypt-nexus-6p/ Props go out to that team.
Sent from my Nexus 6P using Tapatalk

Problem with TWRP mounting (mmcblk0p39)

Trying to flash a custom ROM, actually, when flashing pretty much all ROMS with 3.0.2, I get the following error: "mount: Failed to mount /dev/block/mmcblk0p39 at /cust: Device or resource busy" I believed this didn't pose a problem, since all ROMs had flashed fine, or so I thought, until I tried to flash one of HTCMania's customs and it had to change the system font, but didn't. Any ideas as to why this may be happening? Or how can this be fixed?

KillerDam said:
Trying to flash a custom ROM, actually, when flashing pretty much all ROMS with 3.0.2, I get the following error: "Failed to mount /dev/block/mmcblk0p39 at /cust: Device or resource busy" I believed this didn't pose a problem, since all ROMs had flashed fine, or so I thought, until I tried to flash one of HTCMania's customs and it had to change the system font, but didn't. Any ideas as to why this may be happening? Or how can this be fixed?
Click to expand...
Click to collapse
i have same problem in twrp,but with data,i have fix that by flash stock recovery,from stock recovery i have made wipe data factory reset and wipe cache and he work,it might work for you,so give a try

cristi.blidariu said:
i have same problem in twrp,but with data,i have fix that by flash stock recovery,from stock recovery i have made wipe data factory reset and wipe cache and he work,it might work for you,so give a try
Click to expand...
Click to collapse
How did you flash the stock recovery?

KillerDam said:
How did you flash the stock recovery?
Click to expand...
Click to collapse
By fastboot,and command is fastboot flash recovery recovery.img

cristi.blidariu said:
By fastboot,and command is fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Nope, didn't work, still can't mount cust partition, even after factory reset using stock recovery. I can only think about pushing the rom through sideload, but can't seem to figure out how. I'm about to give up and just return to Lollipop

KillerDam said:
Nope, didn't work, still can't mount cust partition, even after factory reset using stock recovery. I can only think about pushing the rom through sideload, but can't seem to figure out how. I'm about to give up and just return to Lollipop
Click to expand...
Click to collapse
Did you try to flash files via fastboot,or you try to restore your backup via twrp?

cristi.blidariu said:
i have same problem in twrp,but with data,i have fix that by flash stock recovery,from stock recovery i have made wipe data factory reset and wipe cache and he work,it might work for you,so give a try
Click to expand...
Click to collapse
cristi.blidariu said:
Did you try to flash files via fastboot,or you try to restore your backup via twrp?
Click to expand...
Click to collapse
Was trying to flash a ROM via TWRP, ROM flashes, but not correctly, since system font and other assorted things remain unchanged, and they should change.

KillerDam said:
Was trying to flash a ROM via TWRP, ROM flashes, but not correctly, since system font and other assorted things remain unchanged, and they should change.
Click to expand...
Click to collapse
K,wich rom?

cristi.blidariu said:
K,wich rom?
Click to expand...
Click to collapse
I have the same problem while trying to install sokkoban's rom from huaweip8lite blogspot.
After the error message extracting system hangs. After forced restart twrp recovery cannot boot again. Had to debrick my phone. :\

aelfwine88 said:
I have the same problem while trying to install sokkoban's rom from huaweip8lite blogspot.
After the error message extracting system hangs. After forced restart twrp recovery cannot boot again. Had to debrick my phone. :\
Click to expand...
Click to collapse
Edit:
I think this is caused by the install script doesn't unmount /cust mountpoint before trying to access it.

aelfwine88 said:
Edit:
I think this is caused by the install script doesn't unmount /cust mountpoint before trying to access it.
Click to expand...
Click to collapse
Do you have any idea how can it be fixed? Maybe which line could be missing or wrong and what would the correct syntax be.

cristi.blidariu said:
K,wich rom?
Click to expand...
Click to collapse
Nautilus ROM, and maybe Sokkoban's KangVIP iirc

KillerDam said:
Nautilus ROM, and maybe Sokkoban's KangVIP iirc
Click to expand...
Click to collapse
sorry for late answer,Nautilus rom is base on hw/eu location with build number C432B564,you need to flash location https://mega.nz/#!aB9kUDST!q_mT6cq9uEQjvscnbXBZq3B1X6BWsMk7iYKaDjfFzJU flash with twrp,then try to install Nautilus rom,for @sokkoban KangVIP you need chinese location,well i don't have that location you should search your self

KillerDam said:
Do you have any idea how can it be fixed? Maybe which line could be missing or wrong and what would the correct syntax be.
Click to expand...
Click to collapse
I think you need to unmount /cust before you start to work with it. I checked the original Chinese rom which was it converted from and those guys are unmounting all mountpoins in the beginning of the install script (META-INF\com\google\android\updater-script):
Code:
ifelse(is_mounted("/data"), unmount("/data"));
ifelse(is_mounted("/system"), unmount("/system"));
ifelse(is_mounted("/cust"), unmount("/cust"));
This goes before the "ui_print("Formatting cust...");" line.
Sokkoban doesn't do it in his script so I thing that should be the problem.
I just switched my location to cn the other day and tried to install the new KangVIP B569. It went well, but i couldn't figure out how to install gapps (and I needed my phone live again...) so I switched back sokoban's modded KangVIP B564 version which has the same error during install. But it didn't stucked this time at extracting system and I guess it flashed /cust fine as well. And that was at 3am and I did not have the spirit to try to fix the script and flash again... Anyway you can try the code above but I suggest to switch location to cn and go for the latest KangVIP B569 or sokoban's KangVIP B564 (and you can try the script fix before flash). If you go with KangVIP B569 and you can figure out how to install gapps to please share.
If you stuck with location switching or don't know how to get official cn 6.0 android (also requirement for the modded 6.0) drop me a message and I try to recollect how I done that.
Good luck.

Freezes on Google screen after attempted SU Install from TWRP

Ok I am sure I did this before without any problem, but this time, through TWRP on the NRTK, I installed Magisk, no problems, and then went back to install the SU with the zip file in TWRP again and then on the reboot it freezes on the Google startup screen.
I didnt even want to install the SU zip, but when I ran SU after Magisk installed after reboot, SU gave an error, so I decided to install SU from TWRP.
Did I do something wrong there, so I dont repeat the same error next time?
And how do I get out of this locked state?
I've tried wiping all cache to factory reset without deleting internal storage data... I am hoping I dont have to delete and wipe everything and start all over. I did not have a chance to eve install TiB yet.

Dathaeus said:
Ok I am sure I did this before without any problem, but this time, through TWRP on the NRTK, I installed Magisk, no problems, and then went back to install the SU with the zip file in TWRP again and then on the reboot it freezes on the Google startup screen.
I didnt even want to install the SU zip, but when I ran SU after Magisk installed after reboot, SU gave an error, so I decided to install SU from TWRP.
Did I do something wrong there, so I dont repeat the same error next time?
And how do I get out of this locked state?
I've tried wiping all cache to factory reset without deleting internal storage data... I am hoping I dont have to delete and wipe everything and start all over. I did not have a chance to eve install TiB yet.
Click to expand...
Click to collapse
Flash the stock boot.img from the image/rom you were using before this and reboot. You will have to re-root (properly) afterwards, but your phone should boot up. If you use Magisk, you don't need SU, and vice versa. Use only one method to root.

v12xke said:
Flash the stock boot.img from the image/rom you were using before this and reboot. You will have to re-root (properly) afterwards, but your phone should boot up. If you use Magisk, you don't need SU, and vice versa. Use only one method to root.
Click to expand...
Click to collapse
Hmmm ya I prob should have posted that SU error message instead of what I did, douche move.
But how do I flash the boot.img... I have an original copy of it on my PC... can I somehow while in TWRP on the phone connect to my PC via cable and run commands from my PC in CMD and execute that old boot.img flash? Or is there a location in the stock Nexus already I can use? Because there is no file in the root drive after I did the soft wipe.
P.S. Everything I have done so far has not deleted my whole storage, yet.... not sure if that is necessary at this point bec it seems reflashing the boot.img wipes absolutely everything again? If I have to it is what it is... just painful when this happens before I could get TiB running... unless my Nandroid backup file I have will restore and work after I do this?

Dathaeus said:
Hmmm ya I prob should have posted that SU error message instead of what I did, douche move.
But how do I flash the boot.img... I have an original copy of it on my PC... can I somehow while in TWRP on the phone connect to my PC via cable and run commands from my PC in CMD and execute that old boot.img flash? Or is there a location in the stock Nexus already I can use? Because there is no file in the root drive after I did the soft wipe.
Click to expand...
Click to collapse
While in TWRP you have MTP (file transfer) so you can add files to your device. Transfer the boot.img over to your device via MTP and then use TWRP to flash. Just be sure to select flash IMAGE rather than ZIP. Lesson here is when you get back up and running, install fastboot/adb and make sure it is working well and communicating with your PC. Then you can learn how to use it. This would take literally 5 seconds to flash via fastboot (device in bootloader mode).
---------- Post added at 01:29 PM ---------- Previous post was at 01:26 PM ----------
Dathaeus said:
P.S. Everything I have done so far has not deleted my whole storage, yet.... not sure if that is necessary at this point bec it seems reflashing the boot.img wipes absolutely everything again? If I have to it is what it is... just painful when this happens before I could get TiB running... unless my Nandroid backup file I have will restore and work after I do this?
Click to expand...
Click to collapse
NO, flashing boot.img will not delete any of your files. It will only write to the boot partition. If using fastboot the command is fastboot flash boot boot.img

v12xke said:
While in TWRP you have MTP (file transfer) so you can add files to your device. Transfer the boot.img over to your device via MTP and then use TWRP to flash. Just be sure to select flash IMAGE rather than ZIP. Lesson here is when you get back up and running, install fastboot/adb and make sure it is working well and communicating with your PC. Then you can learn how to use it. This would take literally 5 seconds to flash via fastboot (device in bootloader mode).
NO, flashing boot.img will not delete any of your files. It will only write to the boot partition. If using fastboot the command is fastboot flash boot boot.img
Click to expand...
Click to collapse
Yep I actually had those platform files already, and yes the MTP was active there, I just never tried that before so didnt know it was even a possibility or the right way.
So I tried via flashing my very old boot.img and also the one from
https://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
via TWRP "Install" via image install (not zip) and to the "boot partition"
and no change, same stuck on Google logo screen.
I tried the fastboot command from CMD and it says
< waiting for any device >
and doesnt do anything. I had it on the default TWRP menu screen.... I waited over 20 min although I know it shouldnt take near that long, just in case.
My bootloader is unlocked BTW, I dont want to assume anything here.

You need help getting the latest fastboot/adb binaries working on your PC. So many tutorials on how to do this. Ugh.

Dathaeus said:
Yep I actually had those platform files already, and yes the MTP was active there, I just never tried that before so didnt know it was even a possibility or the right way.
So I tried via flashing my very old boot.img and also the one from
https://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
via TWRP "Install" via image install (not zip) and to the "boot partition"
and no change, same stuck on Google logo screen.
I tried the fastboot command from CMD and it says
< waiting for any device >
and doesnt do anything. I had it on the default TWRP menu screen.... I waited over 20 min although I know it shouldnt take near that long, just in case.
My bootloader is unlocked BTW, I dont want to assume anything here.
Click to expand...
Click to collapse
Which OS security patch were you running? Flash the system (to the system partition in TWRP) and boot images (again) from the 6P factory image of the same name:
https://developers.google.com/android/images?hl=en
See if this helps.
Sent from my Nexus 5X using Tapatalk

v12xke said:
You need help getting the latest fastboot/adb binaries working on your PC. So many tutorials on how to do this. Ugh.
Click to expand...
Click to collapse
Not sure what you mean... I JUST did all that when I redid my phone completely back to factory etc etc.... just few weeks ago and then again on my new replacement. But just to be sure, I downloaded all those files again today and it didnt make any difference.
Still stuck on the
< waiting for any device >
I have to be missing some other step or something else is wrong here.
FYI not sure if this matters but when phone boots to recovery there's a red error message
"Unable to mount storage"
but it loads to TWRP fine anyways.

SlimSnoopOS said:
Which OS security patch were you running? Flash the system (to the system partition in TWRP) and boot images (again) from the 6P factory image of the same name:
https://developers.google.com/android/images?hl=en
Click to expand...
Click to collapse
Yep thats what I been doing.....
So the CMD command still doesnt work, which I think is weird in itself... and when I try to install from recovery, it goes through the whole process, both boot.img and system.img, but then it freezes on the Google logo again, so no change.
Sorry I am not sure what security patch, I just got this used from eBay, and one thing, not sure if this means anything, it says its a beta version or something and that message came up all the time when I rebooted when the phone was working.

Do I need to suck it up and redo the whole phone again........ :/

Database Users

welcome