Related
Hi everybody!! I have a BIG issue: my nexus 4 is unlocked, with the CWM recovery and CyanogenMod 10.1 installed. Due to some technical problems, I decided to flash the factory rom again (following this guide http://forum.xda-developers.com/showthread.php?t=2010312) but I can't do it!! Indeed when I try to flash the factory rom the prompt says
file:could not allocate 544035848 bytes
error:cannot load system.img :not enough space
And when i checked the system capacity the result is that my system partition doesn't exist (as you can see on the pic attached)!
I wish to send my phone back to google with the RMA (it was delivered 7 days ago) but I'm not sure that the warranty is still valid (what do you think about that?). Indeed there is no OS now, and everything is unlocked.
Anybody could help me?
Thanks a lot!!
StefanoRedi said:
Hi everybody!! I have a BIG issue: my nexus 4 is unlocked, with the CWM recovery and CyanogenMod 10.1 installed. Due to some technical problems, I decided to flash the factory rom again (following this guide http://forum.xda-developers.com/showthread.php?t=2010312) but I can't do it!! Indeed when I try to flash the factory rom the prompt says
file:could not allocate 544035848 bytes
error:cannot load system.img :not enough space
And when i checked the system capacity the result is that my system partition doesn't exist (as you can see on the pic attached)!
I wish to send my phone back to google with the RMA (it was delivered 7 days ago) but I'm not sure that the warranty is still valid (what do you think about that?). Indeed there is no OS now, and everything is unlocked.
Anybody could help me?
Thanks a lot!!
Click to expand...
Click to collapse
use the fastboot commands to erase system, boot, and data. then use flashboot to flash bootloader, then stock recovery, then stock system.
EvoXOhio said:
use the fastboot commands to erase system, boot, and data. then use flashboot to flash bootloader, then stock recovery, then stock system.
Click to expand...
Click to collapse
Thanks!! Just a couple of questions: 1. the prompt commands are "fastboot erase system" "fastboot erase boot" and "fastboot erase data", right? 2. Have I to reboot the system between every erase and every flash?
StefanoRedi said:
Thanks!! Just a couple of questions: 1. the prompt commands are "fastboot erase system" "fastboot erase boot" and "fastboot erase data", right? 2. Have I to reboot the system between every erase and every flash?
Click to expand...
Click to collapse
That sounds right but Fiona search to be safe. No reboots needed.
StefanoRedi said:
Thanks!! Just a couple of questions: 1. the prompt commands are "fastboot erase system" "fastboot erase boot" and "fastboot erase data", right? 2. Have I to reboot the system between every erase and every flash?
Click to expand...
Click to collapse
I tryed to do it without results. I attach the screen.
Have you some other advises? I really don't know what i can do it with my phone. If i send it back to google, do you think that they will check if my phone is locked/unlocked, with/without os, ecc? Because I'm afraid to have wasted my money!
Have you tried booting into recovery and wiping everything before flashing system? Also you're sure you have the right system.img? Maybe re-download the files from google and try again?
---------- Post added at 09:23 AM ---------- Previous post was at 09:22 AM ----------
also, do you have any nandroids or downloaded ROMs on the phone? If so, you could try flashing CWM, and then booting into it and restoring the nandroid or installing a ROM.
R: Cannot flash system.img, df shows no system partition
We tried wiping everything trough fast boot, he does not have any nandroid backup and I think he tried to flash another ROM (cm) with no luck.
We downloaded the right images, we tried both 4.2.1 and JOP40D from the Google site and from the mirror that we found in some thread here on xda.
(I'm his friend and I was helping him via Skype, that's why I know these informations)
I think now we'll try to flash cwm and wipe everything trough it and install a stock ROM or a custom one.
Ty for the help.
Sent from my Nexus 4
squalluca said:
We tried wiping everything trough fast boot, he does not have any nandroid backup and I think he tried to flash another ROM (cm) with no luck.
We downloaded the right images, we tried both 4.2.1 and JOP40D from the Google site and from the mirror that we found in some thread here on xda.
(I'm his friend and I was helping him via Skype, that's why I know these informations)
I think now we'll try to flash cwm and wipe everything trough it and install a stock ROM or a custom one.
Ty for the help.
Sent from my Nexus 4
Click to expand...
Click to collapse
It really sounds like someone made a mistake and ran the wrong command and actually remove the /system partition. Not erased or formatted, but actually removed the mount point. I'm sure there is a way to recreate it, but I have no idea how.
R: Cannot flash system.img, df shows no system partition
That's what I think too... this error appeared before we tried any wipe/erase command trough fastboot... hope someone can help us in recrate the mount point for the system partition...
Sent from my Nexus 4
EvoXOhio said:
It really sounds like someone made a mistake and ran the wrong command and actually remove the /system partition. Not erased or formatted, but actually removed the mount point. I'm sure there is a way to recreate it, but I have no idea how.
Click to expand...
Click to collapse
Thanks guys! I really hope that someone knows how to recreate it and, if it's possibile, very soon, because the RMA expiration day is coming!!
This is generally to be avoided, but I think this may actually be a last resort situation. Download the full factory image extract down a few levels until you have flash-all.bat extracted, at that point you'll also see the radio, bootloader, an image zip, and some linux scripts. Make sure you've actually extracted them and that you aren't just looking in the zip. Run flash-all.bat Don't touch anything until it's done, if you disrupt the write to bootloader or possibly radio, you brick.
By the way, the factory image is here and you may need to use 7zip to extract it. 7zip will have shell integration, so just right click what you want, drop down to 7zip and extract to.
Also, you may be able to accomplish the same thing with:
Code:
fastboot -w update image-occam-jop40c.zip
so maybe try that first.
USSENTERNCC1701E said:
This is generally to be avoided, but I think this may actually be a last resort situation. Download the full factory image extract down a few levels until you have flash-all.bat extracted, at that point you'll also see the radio, bootloader, an image zip, and some linux scripts. Make sure you've actually extracted them and that you aren't just looking in the zip. Run flash-all.bat Don't touch anything until it's done, if you disrupt the write to bootloader or possibly radio, you brick.
By the way, the factory image is here and you may need to use 7zip to extract it. 7zip will have shell integration, so just right click what you want, drop down to 7zip and extract to.
Also, you may be able to accomplish the same thing with:
Code:
fastboot -w update image-occam-jop40c.zip
so maybe try that first.
Click to expand...
Click to collapse
Fine, I will try when I come back home. Just a question: what do you think about the warranty? Do you think that google will check if the phone is unlocked and without os? It is better for me risk with the last suggested process and (maybe) brick the phone or send it back as it is now? It's because I'm just a beginner with mod, scripts, prompts, ecc..sorry!
StefanoRedi said:
Fine, I will try when I come back home. Just a question: what do you think about the warranty? Do you think that google will check if the phone is unlocked and without os? It is better for me risk with the last suggested process and (maybe) brick the phone or send it back as it is now? It's because I'm just a beginner with mod, scripts, prompts, ecc..sorry!
Click to expand...
Click to collapse
The phone was damaged from user error. It is unethical and probably illegal to RMA it. Try to fix it yourself, and if you can't, man up and buy a new phone. RMAs are for faulty products, not products ruined by an inexperienced user doing something wrong.
EvoXOhio said:
The phone was damaged from user error. It is unethical and probably illegal to RMA it. Try to fix it yourself, and if you can't, man up and buy a new phone. RMAs are for faulty products, not products ruined by an inexperienced user doing something wrong.
Click to expand...
Click to collapse
You are completely right. I wrote that just because I messed up the phone (following guides, using toolkit, using cmd in a proper way) trying to fix it (from the first day it was impossible to call due to microphone/speaker software problem). And sometimes, while a was doing the same stuff that everybody do with good results, the phone didn't do what it was supposed to do. Consequently I wanted to RMA it because i think it's my fault (I know it and I admit it) but not completely. I really don't want to cheat anyone.
Well, I fixed it. I don't know the reason but the day after everything was fine (maybe it's because I erased everything from CWM; i wiped everything and then i wen on Mount and I erased everything). Btw, the day after I reflashed everything from prompt with the phone in fastboot and i flashed also system (the partition was "avaible" again); the .img flashed was the factory rom 4.2.0. Then I reboot it but the problem with microphone/speacker wasn't fixed; i updated to 4.2.1 and it still didn't work. Today I will call google to RMA it because now (just now) the phone is not working properly but not due to my errors. Thanks to everybody!!!! :laugh:
StefanoRedi said:
Well, I fixed it. I don't know the reason but the day after everything was fine (maybe it's because I erased everything from CWM; i wiped everything and then i wen on Mount and I erased everything). Btw, the day after I reflashed everything from prompt with the phone in fastboot and i flashed also system (the partition was "avaible" again); the .img flashed was the factory rom 4.2.0. Then I reboot it but the problem with microphone/speacker wasn't fixed; i updated to 4.2.1 and it still didn't work. Today I will call google to RMA it because now (just now) the phone is not working properly but not due to my errors. Thanks to everybody!!!! :laugh:
Click to expand...
Click to collapse
Make sure flash stock recovery and relock the device before sending it in.
EvoXOhio said:
Make sure flash stock recovery and relock the device before sending it in.
Click to expand...
Click to collapse
Of course! In theory it will not be a problem if there is the CWM recovery and if the phone it's unlucked (at least, I read that for Google and LG is not a problem), but I flashed the stock recovery and then I lucked the phone again. Thanks for your advises.
system.img cannot load, not enough space error
StefanoRedi said:
Well, I fixed it. I don't know the reason but the day after everything was fine (maybe it's because I erased everything from CWM; i wiped everything and then i wen on Mount and I erased everything). Btw, the day after I reflashed everything from prompt with the phone in fastboot and i flashed also system (the partition was "avaible" again); the .img flashed was the factory rom 4.2.0. Then I reboot it but the problem with microphone/speacker wasn't fixed; i updated to 4.2.1 and it still didn't work. Today I will call google to RMA it because now (just now) the phone is not working properly but not due to my errors. Thanks to everybody!!!! :laugh:
Click to expand...
Click to collapse
hey can anyone help me i have this error when i flash Stock 5.0.1 Lollipop, Kitkat flashing is working!
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:
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
Hi, I am in the process of preparing for upgrading from 7.0 to 7.1.1
I know I need to replace the Custom Kernel with the Stock Kernel. And I have to replace TWRP with Stock Recovery.
Can anybody tell me, which file inside the FTF is the stock recovery? I already found the kernel. Need help to find the stock recovery, thank you!
tempurastyle said:
Need help to find the stock recovery, thank you!
Click to expand...
Click to collapse
We don't have one which is why we have to use TWRP.
So my only way is to flash via Flashtool without wipe?
tempurastyle said:
So my only way is to flash via Flashtool without wipe?
Click to expand...
Click to collapse
Do that then mod your own kernel. [How To] make your own XPERIA DRM-fix kernel.
And flash a TWRP.img to the recovery partition.
fotakernel.sin reside's where we flash twrp on stock. you do not need to flash it to upgrade, contrary you can exclude it in flashtool and keep twrp between updates.
realtuxen said:
fotakernel.sin reside's where we flash twrp on stock. you do not need to flash it to upgrade, contrary you can exclude it in flashtool and keep twrp between updates.
Click to expand...
Click to collapse
this is real knowledge, thanks! so just to be sure, this is what i will do in flashtool:
1) wipe: nothing selected
2) exclude: fotakernel.sin selected
can anybody confirm this is correct?
then after this, i will flash a custom kernel via fastboot and magisk via twrp.
one question regarding magisk: will it be deleted during the flashtool update?
So I ran into a problem...
The Upgrade to 7.1.1 via flashtool was smooth. Then, i flashed twrp via fastboot as usual. When I tried to enter twrp, i get a password prompt to decrypt the phone. So i don't know which password i need to type in. I tried the unlock PIN, doesnt work. Any suggestions?
tempurastyle said:
Any suggestions?
Click to expand...
Click to collapse
To get round that you need to run the following commands...
Code:
fastboot format userdata
fastboot format cache
...so you'll need to backup all your data first.
XperienceD said:
To get round that you need to run the following commands...
Code:
fastboot format userdata
fastboot format cache
...so you'll need to backup all your data first.
Click to expand...
Click to collapse
Ok, so I decided to keep my data and don't install twrp. Now I got another issue, is it possible to install Magisk without TWRP? I already got my kernel using my ta backup according to the instructions a few posts above, which really works great.
tempurastyle said:
Ok, so I decided to keep my data and don't install twrp. Now I got another issue, is it possible to install Magisk without TWRP? I already got my kernel using my ta backup according to the instructions a few posts above, which really works great.
Click to expand...
Click to collapse
I thought you excluded fotakernel so you did not have to flash twrp again. Oh well anyway you can use twrp to flash zips just fine although /data is encrypted, most flash zips do not write to /data anyway some like supersu use /cache (which is not encrypted contrary to the info above) to get around encryption at next boot. And like magisk also patch the boot.img live on your phone, some write to /system which is not encrypted either, I never seen a flash zip that did write to /data. Only backup/browsing/etc on /data is affected.
So when presented with the password screen in twrp just press cancel and make sure the zip you want to flash is located on the external sd card (do not encrypt this in phone settings, your card will be unreadable from pcs to) then choose flash zip and choose the external sdcard to pick the zip from and flash magisk or whatever. You need to run your kernel through ta poc or rootkernel first and disable dm verity and sony ric. (you write you did this so just install twrp and flash away) Do not wipe cache before rebooting just in case magisk uses this in a similar way to supersu (I have no idea)
Also if you do the above fastboot format commands suggested in post#8 without disabling 'forceencrypt' for /data (fstab in the kernel image or with a tool) the phone will encrypt itself again as soon as you turn it on.
If forceencrypt is disabled the same can be achieved (clearing encryption) with a factory reset btw.
So if you did not bump into the password in twrp before you likely did a factory reset with a kernel with encryption disabled. Then, maybe after updating you rebooted stock and the phone encrypted itself again, then now you can not access /data in twrp. Thats also because we have no version of it that supports encryption on the X-compact though. Again do not worry, I have not meet a zip I could not flash, supersu, magisk, etc because they do not access /data anyway.
realtuxen said:
I thought you excluded fotakernel so you did not have to flash twrp again. Oh well anyway you can use twrp to flash zips just fine although /data is encrypted, most flash zips do not write to /data anyway some like supersu use /cache (which is not encrypted contrary to the info above) to get around encryption at next boot. And like magisk also patch the boot.img live on your phone, some write to /system which is not encrypted either, I never seen a flash zip that did write to /data. Only backup/browsing/etc on /data is affected.
So when presented with the password screen in twrp just press cancel and make sure the zip you want to flash is located on the external sd card (do not encrypt this in phone settings, your card will be unreadable from pcs to) then choose flash zip and choose the external sdcard to pick the zip from and flash magisk or whatever. You need to run your kernel through ta poc or rootkernel first and disable dm verity and sony ric. (you write you did this so just install twrp and flash away) Do not wipe cache before rebooting just in case magisk uses this in a similar way to supersu (I have no idea)
Click to expand...
Click to collapse
Yes, after the first upgrade attempt, i let twrp untouched. then when entering twrp, i didnt have a password, so i skipped it. i couldn't find the sd card in the file browser, and after i hit reboot in twrp the phone restarted and got stuck in boot.
So I flashed again, this time deleting twrp. the initial boot up went fine. Then i flashed twrp again and once again, without having a password, i just skipped the password prompt. still couldnt find the sd card, and i rebooted out of twrp. and the phone got stuck again.
after 2-3 trials, i figured out that everytime i rebooted out of twrp, the phone gets stuck during boot. even after turning it off and on, so a reflash was needed.
now i have given up using twrp, so i have an unrooted phone with an unlocked bootloader. which does not allow me to use android pay. i think to solve my problem is:
1) i need to know which twrp version really works, i have tried
this version
and this version
both cause a boot failure for me
2) i need to find the sd card location in the twrp file browser (all the folders show empty for me)
if nothing works, i guess i need to wipe my phone, but that's what i would like to avoid. thanks for your help guys!
tempurastyle said:
Yes, after the first upgrade attempt, i let twrp untouched. then when entering twrp, i didnt have a password, so i skipped it. i couldn't find the sd card in the file browser, and after i hit reboot in twrp the phone restarted and got stuck in boot.
So I flashed again, this time deleting twrp. the initial boot up went fine. Then i flashed twrp again and once again, without having a password, i just skipped the password prompt. still couldnt find the sd card, and i rebooted out of twrp. and the phone got stuck again.
after 2-3 trials, i figured out that everytime i rebooted out of twrp, the phone gets stuck during boot. even after turning it off and on, so a reflash was needed.
now i have given up using twrp, so i have an unrooted phone with an unlocked bootloader. which does not allow me to use android pay. i think to solve my problem is:
1) i need to know which twrp version really works, i have tried
this version
and this version
both cause a boot failure for me
2) i need to find the sd card location in the twrp file browser (all the folders show empty for me)
if nothing works, i guess i need to wipe my phone, but that's what i would like to avoid. thanks for your help guys!
Click to expand...
Click to collapse
The 2. issue with the sdcard is easy. After pressing 'install' button in twrp at the bottom left press the "select storage' button, a small window will pop up then select the 'micro sdcard' and press 'ok", you should see your files now.
The 1. ssue is really odd! I use the second twrp you posted, for some wierd reason the first one does not boot for me (twrp does not start). But I talked with another guy for him it was the other way around. It was really strange. I think most can use both though without problems
There is one more twrp 3.1 from bambamx, but I really do not get this, twrp boots from its own partition with its own kernel. They should be separated unless twrp does something to system ofcause which it very well shouldn't unless you ask it to, deleting a important file or flashing something. I have never heard of this sorry. One thing is certain our device sure could use a stable nougat encryption compatible twrp!
I will let you know if I find something, you can try the last available version, I have no idea if it will exhibit the same strange behaviour. But maybe its worth a shot although it seems something else is at play.
A couple of stupid questions sorry; You disabled dm verity and sony ric in ta poc right, and it does not happen if you boot your phone normal a couple of times.
Edit: sorry Mr. Sandman had not left so I did not read properly here from the morning. I will edit my post to actually answer as best as I can lol.
Just to let you know:
1. You do not need to install TWRP to use it! You can just do
Code:
fastboot boot <TWRP image>
to run TWRP on the phone (instead of
Code:
fastboot flash boot <TWRP image>
). The only drawback of this method is that you will always need a computer to enter TWRP. Btw. with this method you can also try out a custom kernel image before flashing it.
2. You do not need write access to /data partition to install Magisk. It was explained in another thread that Magisk can use /cache temporary when access to /data is not available. It will write to /data on first boot instead.
3. While using TWRP you can use adb to transfer files onto the phone, so you don't need to have them ready on the internal storage.
realtuxen said:
The 2. issue with the sdcard is easy. After pressing 'install' button in twrp at the bottom left press the "select storage' button, a small window will pop up then select the 'micro sdcard' and press 'ok", you should see your files now.
Click to expand...
Click to collapse
I did, but the SD card can't be selected, and the size shows as 0kb. I did a workaround though: i formatted a spare sd card and copied magisk on it. it was instantly recognized and selectable.
ypnos42 said:
Just to let you know:
1. You do not need to install TWRP to use it! You can just do
Code:
fastboot boot <TWRP image>
to run TWRP on the phone (instead of
Code:
fastboot flash boot <TWRP image>
). The only drawback of this method is that you will always need a computer to enter TWRP. Btw. with this method you can also try out a custom kernel image before flashing it.
3. While using TWRP you can use adb to transfer files onto the phone, so you don't need to have them ready on the internal storage.
Click to expand...
Click to collapse
GREAT advice! I launched TWRP from ADB and successfully flashed Magisk using ADB sideload. Thanks, my phone is rooted again!
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........ :/