So I flashed a factory image on my Nexus, and when it boots it tells me this, it should be unrooted and un tampered in every way because of the restore! But my device tells me this on boot? Why is that and how do I fix this? Thanks! Please help! Here's my flash process.
fastboot flash bootloader
fastboot reboot-bootloader
fastboot flash radio
fastboot reboot-bootloader
fastboot flash system
fastboot flash recovery
fastboot format userdata
fastboot erase cache
fastboot flash boot
fastboot reboot
I should also add that I had multirom installed previously, if this changes anything.
fastboot flash boot boot.img, fastboot flash system systen.img, etc... Your commands are wrong
Sent from my Nexus 6 using Tapatalk
blueyes said:
fastboot flash boot boot.img, fastboot flash system systen.img, etc... Your commands are wrong
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
My syntax was right, I did it that way I just didn't add the file names in my original post, sorry about that haha I did fastboot flash system system.img and so forth.
And you don't use erase, use format.. Really no need to erase/format if your flashing an image
Sent from my Nexus 6 using Tapatalk
blueyes said:
And you don't use erase, use format.. Really no need to erase/format if your flashing an image
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
erasing or formatting the cache partition isn't needed?
Don't need to format cache if your flashing cache.img. Going to be wiped with new img
Sent from my Nexus 6 using Tapatalk
blueyes said:
Don't need to format cache if your flashing cache.img. Going to be wiped with new img
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I tend to just wipe it and not flash the img. I never flash the cache img, is this most likely the error?
I just flashed elementalx kernel and a supersu zip to remove the corruption message, the device is fine now, but I'm wondering why it said corrupt in the first place.
Common with stock kernel and root
Sent from my Nexus 6 using Tapatalk
blueyes said:
Common with stock kernel and root
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It gave me this error message before the device was rooted though, the device was clean at that point. I rooted after seeing that message. I installed elementalx kernel to get rid of the message and THEN rooted it.
H4X0R46 said:
It gave me this error message before the device was rooted though, the device was clean at that point. I rooted after seeing that message. I installed elementalx kernel to get rid of the message and THEN rooted it.
Click to expand...
Click to collapse
you dont read around xda or do any reseach, do you? lol! its because its been asked in many threads that have been started in this section. its something new that google has added to matshmallow. itll appear if your bootloader is unlocked, if you are using the stock kernel.
simms22 said:
you dont read around xda or do any reseach, do you? lol! its because its been asked in many threads that have been started in this section. its something new that google has added to matshmallow. itll appear if your bootloader is unlocked, if you are using the stock kernel.
Click to expand...
Click to collapse
I usually do but to be honest, I just kinda flipped and posted this in a hurry haha sorry man xD I'll read around next time! Thanks for saving my @$$ anyway lol so it's just the bootloader that triggers that? I knew marshmallow added those messages to it's kernel, I knew about that, had no clue that the open bootloader triggers it! Thanks!
simms22 said:
you dont read around xda or do any reseach, do you? lol! its because its been asked in many threads that have been started in this section. its something new that google has added to matshmallow. itll appear if your bootloader is unlocked, if you are using the stock kernel.
Click to expand...
Click to collapse
Also, I got the red error, did some reading and I should have gotten the orange one shouldn't I?
H4X0R46 said:
Also, I got the red error, did some reading and I should have gotten the orange one shouldn't I?
Click to expand...
Click to collapse
orange/red? maybe youre red is someone elses orange? honestly, ive no idea, as ive never gotten it. but.. i did find the image in the system partition. did it look like this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
simms22 said:
orange/red? maybe youre red is someone elses orange? honestly, ive no idea, as ive never gotten it. but.. i did find the image in the system partition. did it look like this?
Click to expand...
Click to collapse
It was that exact screen yes! I wonder why I got that one because this was after a fresh stock rom flash! Everything stock, although, I did just use fastboot format userdata and fastboot erase cache instead of flashing the cache.img and userdata.img. could this matter?
Sent from my Nexus 6 using XDA Free mobile app
(Ignore this)
H4X0R46 said:
It was that exact screen yes! I wonder why I got that one because this was after a fresh stock rom flash! Everything stock, although, I did just use fastboot format userdata and fastboot erase cache instead of flashing the cache.img and userdata.img. could this matter?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
na, that wouldnt matter. i didnt see it because i flashed a custom kernel the first flash(i think).
simms22 said:
na, that wouldnt matter. i didnt see it because i flashed a custom kernel the first flash(i think).
Click to expand...
Click to collapse
I'm just worried that it is a corrupted part of my phone, I'm hoping it's just a false thing though. The phone boots and everything works fine, just wanting to be sure haha
Sent from my Nexus 6
H4X0R46 said:
I'm just worried that it is a corrupted part of my phone, I'm hoping it's just a false thing though. The phone boots and everything works fine, just wanting to be sure haha
Sent from my Nexus 6
Click to expand...
Click to collapse
it is a false thing
Related
Motorola Atrix Fastboot Tool
Here's a simple batch script I wrote to make it easy for users to erase partitions, flash the pdsfix, and flash Romracer's recovery.
Features:
- Erase /boot
- Erase /radio
- Erase /system
- Erase /userdata
- Erase /cache
- Erase /webtop
- Erase /preinstall
- Erase /sdcard
- Flash pds image from Atrix devkit
- Flash Romracer's Recovery (6 color options)
Downloads:
With Romracer's Recovery 5.0.2.3-atrix4.1 Images:
http://dl.dropbox.com/u/7945325/atrix-fastboot-tool-with-recovery.zip (.zip)
http://dl.dropbox.com/u/7945325/atrix-fastboot-tool-with-recovery.7z (.7z)
Without Recovery Images:
http://dl.dropbox.com/u/7945325/atrix-fastboot-tool-no-recovery.zip (.zip)
http://dl.dropbox.com/u/7945325/atrix-fastboot-tool-no-recovery.7z (.7z)
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's pretty basic but if you find any bugs or have any suggestions let me know.
Ecstacy42 said:
Motorola Atrix Fastboot Tool
Here's a simple batch script I wrote to make it easy for users to erase partitions, flash the pdsfix, and flash Romracer's recovery.
Features:
- Erase /boot
- Erase /radio
- Erase /system
- Erase /userdata
- Erase /cache
- Erase /webtop
- Erase /preinstall
- Erase /sdcard
- Flash pdsfix.img from Atrix devkit
- Flash Romracer's Recovery (6 color options)
Downloads:
With Romracer's Recovery 5.0.2.3-atrix4.1 Images:
http://dl.dropbox.com/u/7945325/atrix-fastboot-tool-with-recovery.zip
Without Recovery Images:
http://dl.dropbox.com/u/7945325/atrix-fastboot-tool-no-recovery.zip
Screenshot:
It's pretty basic but if you find any bugs or have any suggestions let me know.
Click to expand...
Click to collapse
Cool. Maybe you can add the options on the automatic bootloader unlocker as well... all in one kind of thing...
Sent from my Xoom using XDA Premium App
Thanks, I'll try this out instead of doing it manually. What exactly is the "PDS Fix" anyway?
GeNiO426 said:
Thanks, I'll try this out instead of doing it manually. What exactly is the "PDS Fix" anyway?
Click to expand...
Click to collapse
No problem, it does the same thing as doing it manually just saves time.
The pds fix is for people who are having touch screen/soft button issues and didn't backup their pds when they first got their phone. It flashes the pds image from the Atrix Development Kit to fix the issue except your Wifi mac address, Bluetooth mac address, IEMI, and a few other things I don't know of get set to the ones in the Dev Kit. It's not recommended unless you have to.
Ecstacy42 said:
No problem, it does the same thing as doing it manually just saves time.
The pds fix is for people who are having touch screen/soft button issues and didn't backup their pds when they first got their phone. It flashes the pds image from the Atrix Development Kit to fix the issue except your Wifi mac address, Bluetooth mac address, IEMI, and a few other things I don't know of get set to the ones in the Dev Kit. It's not recommended unless you have to.
Click to expand...
Click to collapse
Oh, OK. Thanks for taking the extra time to explain. It's appreciated.
I forgot to include AdbWinApi.dll and AdbWinUsbApi.dll. I added those and added downloads in .7z for those who want a smaller file size. I might add a bootloader unlocker in the near future.
filmusikat said:
Cool. Maybe you can add the options on the automatic bootloader unlocker as well... all in one kind of thing...
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
+1 on this! would be nice, if possible!
my bootloader is unlocked , how can i do this ?
Ecstacy42 said:
I forgot to include AdbWinApi.dll and AdbWinUsbApi.dll. I added those and added downloads in .7z for those who want a smaller file size. I might add a bootloader unlocker in the near future.
Click to expand...
Click to collapse
milad_sr71 said:
my bootloader is unlocked , how can i do this ?
Click to expand...
Click to collapse
Add those files? Personally, I just found the one file that was missing and copied it to the folder and now everything works fine. They're included in the update, though.
When I try to flash romracers recovery it fails at erasing /recovery and writing recovery. I wanted to sell my Atrix so I was going to return it to stock. I tried flashing the 2.3.4 sbf and now I can't get the phone to boot past the dual core screen it's stuck in a boot loop. I can access all the options you get when you hold volume down on startup but I can't get into recovery. When I try to I get a screen showing a white triangle with a yellow exclamation point inside and the android guy under it.
ETA: After looking up what the recovery screen means it looks like I have no recovery. Does anyone know why this tool is failing for me or how get it out of the boot loop?
LSUtigers03 said:
When I try to flash romracers recovery it fails at erasing /recovery and writing recovery. I wanted to sell my Atrix so I was going to return it to stock. I tried flashing the 2.3.4 sbf and now I can't get the phone to boot past the dual core screen it's stuck in a boot loop. I can access all the options you get when you hold volume down on startup but I can't get into recovery. When I try to I get a screen showing a white triangle with a yellow exclamation point inside and the android guy under it.
ETA: After looking up what the recovery screen means it looks like I have no recovery. Does anyone know why this tool is failing for me or how get it out of the boot loop?
Click to expand...
Click to collapse
Try fastboot erasing everything, flashing the 2.3.4 SBF again, let it fully finish until it says PASS, if your able to boot leave it at that, don't try unlocking it or flashing recovery or anything.
Ecstacy42 said:
Try fastboot erasing everything, flashing the 2.3.4 SBF again, let it fully finish until it says PASS, if your able to boot leave it at that, don't try unlocking it or flashing recovery or anything.
Click to expand...
Click to collapse
The phone is already unlocked so I wouldn't have to do that again. When flashing the SBF everything finishes until the end when RSD says to manually reboot the phone. That's when it starts the boot loop. When I took the battery out and restarted the phone RSD said PASS but the boot loops didn't stop. Also I noticed that the version of RSD I was using had a blue icon and I downloaded 5.5 and it has a red icon. Idk maybe it's the version of RSD that was the issue. I'll try it again.
---------- Post added at 02:52 PM ---------- Previous post was at 02:31 PM ----------
ETA:Well I did the exact same thing as before except this time I used the SBF and RSD Lite from the pudding thread and everything went smoothly.
LSUtigers03 said:
The phone is already unlocked so I wouldn't have to do that again. When flashing the SBF everything finishes until the end when RSD says to manually reboot the phone. That's when it starts the boot loop. When I took the battery out and restarted the phone RSD said PASS but the boot loops didn't stop. Also I noticed that the version of RSD I was using had a blue icon and I downloaded 5.5 and it has a red icon. Idk maybe it's the version of RSD that was the issue. I'll try it again.
---------- Post added at 02:52 PM ---------- Previous post was at 02:31 PM ----------
ETA:Well I did the exact same thing as before except this time I used the SBF and RSD Lite from the pudding thread and everything went smoothly.
Click to expand...
Click to collapse
So everything works as it should now? Good.
What were you using to flash the SBF before if you weren't using RSD Lite?
Ecstacy42 said:
So everything works as it should now? Good.
What were you using to flash the SBF before if you weren't using RSD Lite?
Click to expand...
Click to collapse
I was using RDS Lite but I think it may have been an older version or it could have been the SBF. The original SBF I used was from the Firmware Superthread and the one that worked was from the pudding thread. I'm not sure what the issue was but the phone is restored and working fine now. Thanks for the help.
Does anyone know if - Erase /boot = "fastboot -w" ?
Nipit said:
Does anyone know if - Erase /boot = "fastboot -w" ?
Click to expand...
Click to collapse
Nice thread Resurrection, but no. The erase data should be fastboot -w as it only deletes cache and userdata
So erase cache & userdata will be the same as fastboot -w, right?
Nipit said:
So erase cache & userdata will be the same as fastboot -w, right?
Click to expand...
Click to collapse
Exactly but coolnow just answered that question.
Ecstacy42 said:
Exactly but coolnow just answered that question.
Click to expand...
Click to collapse
I just wanted to be sure, because somehow through CMD when I type fastboot -w it just says waiting for the device... But my device is connected and all drivers are installed.
Nipit said:
I just wanted to be sure, because somehow through CMD when I type fastboot -w it just says waiting for the device... But my device is connected and all drivers are installed.
Click to expand...
Click to collapse
Make sure your phone is in fastboot mode
Sent from my MB860 using xda premium
I unlocked the bootloader, flashed CWM recovery, took a backup.
Factory reset, wiped cache, dalvik cache and then installed CM10 build#3 from here. I had extracted the boot.img so I did flash the boot using fastboot but it says
sudo fastboot flash boot boot.img
sending 'boot' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 0.000s
Next, when I boot the device normally, it gets stuck on the white screen with HTC displayed on it.
So I went back into recovery, wiped everything again and installed the ROM again. This was repeated a few times, but to no avail.
I use only Linux on my laptop, not Windows so HTC Sync and stuffs strictly related to Windows do not apply. Now, I have these options:
1. Either I restore my phone to the saved backup successfully, but CWM won't let me do it. It exits with the common MD5 mismatch. And I don't have an SD card reader. So is it possible to boot my phone via fastboot and mount the SD card somehow and access the backup file so that I can generate the md5 again?
2. Or, next option that I have is to download a ROM which is *working* taking the help of a friend using his SD card(which might delay the process) and install that new ROM on my phone. In that case, please direct me to some such ROMs and the exact way to flash if I did it wrong.
I'd prefer Option 1, so please provide some help for the same.
UPDATE: Generated md5 and restored.
UPDATE #2: Unable to flash boot875.img NOPE kernel after installing CM10 again. Did a full wipe, and installed CM build#3 again and tried flashing boot875.img via fastboot and it doesn't say anything in the terminal.
Your phone was connected via fastboot when you were flashing and was there any problem, like your phone disconnected or something?
Sent from my HTC Desire C using XDA Premium 4 mobile app
Try to do it again don't use USB 3 ports
If Fails Download NOPE Kernel if you didn't already have it
Put in fastboot folder
Download a CM10 ROM e.g. slimbean
Flash it in recovery
Flash kernel through fastboot
Sent from my GT-P3110 using xda app-developers app
rudi_j7 said:
Your phone was connected via fastboot when you were flashing and was there any problem, like your phone disconnected or something?
Click to expand...
Click to collapse
No. It wasn't disconnected. Installation went butter smooth. Problem occurred while booting.
SiqrCarnbon said:
Try to do it again don't use USB 3 ports
If Fails Download NOPE Kernel if you didn't already have it
Put in fastboot folder
Download a CM10 ROM e.g. slimbean
Flash it in recovery
Flash kernel through fastboot
Click to expand...
Click to collapse
I did use a USB 3 port. Let me try it again using USB 2, and I'll post back the update.
UPDATE: It still says
sudo fastboot flash boot boot.img
sending 'boot' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 0.000s
Anyway I could access my phone's shell using my Linux laptop? adb shell doesn't work. If I enter the shell, I can modify the md5 navigating to the backup directory.
UPDATE: Restored md5.
Redownload kernel
Sent from my HUAWEI Y300-0100 using Tapatalk
SiqrCarnbon said:
Redownload kernel
Click to expand...
Click to collapse
Unable to flash boot875.img NOPE kernel after installing CM10 again. Did a full wipe, and installed CM build#3 again and tried flashing boot875.img via fastboot and it doesn't say anything in the terminal.
While extracting the zip file on my laptop(Linux), I get the following error, starting from the place mentioned in the pic.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sudo?
whi you are using the "sudo" comand?
Don't extract. Just flash the ROM and download a separate nope or Prometheus kernel and flash that.
Sent from my HTC Desire C using XDA Premium 4 mobile app
mareeck said:
whi you are using the "sudo" comand?
Click to expand...
Click to collapse
Even without that, the error persists. I used it once when it was the first command.
rudi_j7 said:
Don't extract. Just flash the ROM and download a separate nope or Prometheus kernel and flash that.
Click to expand...
Click to collapse
Already did that, I flashed the ROM and then tried to flash boot875.img and boot750.img NOPE kernel. Still same error!
When I got error, then I was extracting in laptop just to check the contents of the zip file, and then it said that error as mentioned in picture of the last post.
Try on Windows
I can't help you with Linux As I don't have it installed
Sent from my HUAWEI Y300-0100 using xda app-developers app
4.0.3
u have tried a 4.0.3 rom based. the boot image it will boot for this time, you have to see if the rom is the problem or the the phone is, or maybe the pc, the other thing that can solve it is to relock bootloader, after try to unlock it again and reroot it with the CWM maybe it will help you
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
SiqrCarnbon said:
Try on Windows
I can't help you with Linux As I don't have it installed
Sent from my HUAWEI Y300-0100 using xda app-developers app
Click to expand...
Click to collapse
this may be a good ideea for him
Cm10 doesn't extract properly in terminal or command prompt.... I've tried.... Dunno. Try some other cm based ROM?
Sent from my HTC Desire C using XDA Premium 4 mobile app
SiqrCarnbon said:
Try on Windows
I can't help you with Linux As I don't have it installed
Click to expand...
Click to collapse
mareeck said:
u have tried a 4.0.3 rom based. the boot image it will boot for this time, you have to see if the rom is the problem or the the phone is, or maybe the pc, the other thing that can solve it is to relock bootloader, after try to unlock it again and reroot it with the CWM maybe it will help you
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
this may be a good ideea for him
Click to expand...
Click to collapse
I had already tried relocking bootloader and unlocking it back. It didn't help.
rudi_j7 said:
Cm10 doesn't extract properly in terminal or command prompt.... I've tried.... Dunno. Try some other cm based ROM?
Click to expand...
Click to collapse
Yeah, so I flashed with mini CM10, its booting now, working well. But it is saying No Service for which I had started a thread here http://forum.xda-developers.com/showthread.php?p=50230593
Hello everyone
I believe many people cannot wait to use the latest Android N Preview on their Nexus devices, but found out that root still isn't available. The first root method appears HERE, done by @phhusson.
If people wanted to use SuperSU for some reason, I created this small flashable zip.
Based on nearly the same thoughts but combined with @Chainfire systemless method, this root is also done by setting SELinux to PERMISSIVE.
SuperSU-v2.68-Android-N (fixed)
The zip comes with aroma installer, so you can choose your device within the menu.
Instructions:
(TWRP is working and you're not encrypted) Flash the zip with TWRP directly
(Your device is encrypted, and want to stay encrypted) TWRP will enter a loop. Wait for a while and it will boot eventually, then use adb sideload to flash the zip.
(Your device is encrypted, and you want to decrypt, or TWRP is not working for you) Extract the zip, flash the boot.img for your device through fastboot, then revert to stock recovery. Then do a "Factory Reset" to wipe everything. Now you are decrypted can use TWRP normally.
Features:
Supports Nexus 9, 6P, 6, and 5X
Disabled force-encryption (encrypted users can still use it with no problems)
BusyBox is pre-installed as well.
Tested on my Nexus 9, Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How can i flash zip? How to choose my device please specify
Sent from my Nexus 6 using Tapatalk
ohad129 said:
How can i flash zip? How to choose my device please specify
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Download zip, flash in TWRP.
If encrypted, then use OTG or USB Sideload.
I cant go into my twrp i get the android with red triangle
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:47 PM ---------- Previous post was at 10:32 PM ----------
Ok i think i remember its like was in android m
Sent from my Nexus 6 using Tapatalk
---------- Post added at 11:06 PM ---------- Previous post was at 10:47 PM ----------
Ok i should revert to marashmellow and root then through bera tester get the update so my twrp will stay is it right?
Sent from my Nexus 6 using Tapatalk
I got erorr binary is not install help please
Sent from my Nexus 6 using Tapatalk
I'd love to use this, but I don't have TWRP installed. Is there a working TWRP for the N Preview? TWRP 3.0.0-1 apparently causes bootloops.
anuraj1 said:
I'd love to use this, but I don't have TWRP installed. Is there a working TWRP for the N Preview? TWRP 3.0.0-1 apparently causes bootloops.
Click to expand...
Click to collapse
It will boot up eventually
Wait for a while, TWRP will give up trying to decrypt data after multiple retries.
It will prompt to enter password, press cancel and use adb sideload to flash the zip.
this completely broke the phone for me. cant get through a boot, stuck on boot animation.
couldnt get into recovery. had to reflash a different boot.img to get anything working
not sure what this modified that broke
installing it from TWRP does not work
minieod said:
this completely broke the phone for me. cant get through a boot, stuck on boot animation.
couldnt get into recovery. had to reflash a different boot.img to get anything working
not sure what this modified that broke
Click to expand...
Click to collapse
AJ said:
installing it from TWRP does not work
Click to expand...
Click to collapse
Would you report what models are you using? I'll check if things are messed up. For me on the Nexus 9 it's working good.
You need to rewrite your aroma script, it flashes all of the kernels right after another so the selection doesn't work right. It just causes it not to boot. I edited out everything except for the Nexus 6p from the script and got it to work fine for me.
themustached said:
You need to rewrite your aroma script, it flashes all of the kernels right after another so the selection doesn't work right. It just causes it not to boot. I edited out everything except for the Nexus 6p from the script and got it to work fine for me.
Click to expand...
Click to collapse
Thanks
Super stupid mistake, fixed
I wanted to try N, and at the same time, this post reignited my desire to try without encryption.
How can we keep our nexus updated with encryption off? If i google arround, i just see info from octover 2015, and no newer boot images made (i am currently running stock).
topjohnwu said:
Thanks
Super stupid mistake, fixed
Click to expand...
Click to collapse
I forgot to say, thanks for the installer to begin with. It took a minute to figure out what was happening. It was maddening for a minute.
cocchiararo said:
I wanted to try N, and at the same time, this post reignited my desire to try without encryption.
How can we keep our nexus updated with encryption off? If i google arround, i just see info from octover 2015, and no newer boot images made (i am currently running stock).
Click to expand...
Click to collapse
I fastboot flash bootloader, reboot bootloader,fastboot flas radio,reboot bootloader, fastboot flash boot.IMG,system.IMG, then reboot directly into recovery ,factory reset and flash this
http://forum.xda-developers.com/showthread.php?t=3000788
Then boot up
Sent from my Nexus 6 using XDA Free mobile app
It's boot looping on N6. I manually flashed boot-shamu.img to verify that it wasn't an aroma issue, and it boot looped. I had to flash the original boot.img to get it back.
cjkacz said:
I fastboot flash bootloader, reboot bootloader,fastboot flas radio,reboot bootloader, fastboot flash boot.IMG,system.IMG, then reboot directly into recovery ,factory reset and flash this
http://forum.xda-developers.com/showthread.php?t=3000788
Then boot up
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Ups, never mentioned I am no Nexus 6p
Enviado desde mi Nexus 6P mediante Tapatalk
How do you guys got twrp working on your nexus 9 android N? I tried to flash/boot but it just stucks on twrp logo and restarts to twrp logo bootloop. How can I make twrp work? Thanks
Note - Im still on Android N letting you guys know that I can boot to system from twrp bootloop, all I want is twrp to work so I can restore back to marshmallow. Thanks
cocchiararo said:
Ups, never mentioned I am no Nexus 6p
Enviado desde mi Nexus 6P mediante Tapatalk
Click to expand...
Click to collapse
There is a no encrypt mod for 6p. I'm trying to find it
Edit
http://forum.xda-developers.com/and...-fed-patcher-v8-forceencrypt-disable-t3234422
Sent from my Nexus 6 using Tapatalk
abakash9 said:
How do you guys got twrp working on your nexus 9 android N? I tried to flash/boot but it just stucks on twrp logo and restarts to twrp logo bootloop. How can I make twrp work? Thanks
Note - Im still on Android N letting you guys know that I can boot to system from twrp bootloop, all I want is twrp to work so I can restore back to marshmallow. Thanks
Click to expand...
Click to collapse
I mentioned it in the OP.
Just let it loop a while , it will boot eventually
This is a custom recovery made by LR.Team and I translate the flash tool.
I don't have enough premission so I post it here.
This recovery can automatically decrypt /data partition.
I already tested it on my redmi 6.
Just follow the instruction in the flash tool after you decompress it.
!!UPDATE HERE!!
https://forum.xda-developers.com/redmi-6/development/share-3-3-0-twrp-redmi-6-custom-recovery-t3926225
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Available in Simplified Chinese and English
Link:[url]https://drive.google.com/open?id=18pClwHMAQKNafMq_ng2C0kTlpH_1n-RU[/URL]
Source:[url]http://www.miui.com/thread-19005924-1-1.html[/URL]
Reserved
Thanks for this share. Can you give more details about your usage? Are you running MIUI and did you have to flash Disable DM-Verity? Did you have any difficulties getting this recovery running? E.g. black screen etc.
I had a look at the recovery-twrp flash tool.bat file. It seems to use the usual "fastboot.exe flash recovery" BUT it also flashes an additional file (fastboot.exe flash para misc.bin >NUL 2>NUL) and flashes misc.bin. Can you confirm what misc.bin is and where did you get this custom recovery?
This information would be helpful to everybody else
Yes, I'm running on MIUI 10 and it works perfectly fine for me. Unlike the official TWRP, you don't need to format data for this. So all of your applications and files will still stay in place.
For me, I just went into fastboot mode and use the tool to flash it. Nothing goes wrong.
Also, this recovery use a default password to unlock the /data partition. So you don't have to flash anything else to get this to work.
IDK what is that misc.bin tho
I already linked the source in the post.
seanho12345 said:
Yes, I'm running on MIUI 10 and it works perfectly fine for me. Unlike the official TWRP, you don't need to format data for this. So all of your applications and files will still stay in place.
For me, I just went into fastboot mode and use the tool to flash it. Nothing goes wrong.
Also, this recovery use a default password to unlock the /data partition. So you don't have to flash anything else to get this to work.
IDK what is that misc.bin tho
Click to expand...
Click to collapse
Thanks, I will flash this onto my Redmi 6 when it comes next week
Hi.
How long did it take to flash? 360 hours?
wencesbanger said:
Hi.
How long did it take to flash? 360 hours?
Click to expand...
Click to collapse
You mean unlock bootloader?
seanho12345 said:
You mean unlock bootloader?
Click to expand...
Click to collapse
Yes..
Sorry, my bad.
wencesbanger said:
Yes..
Sorry, my bad.
Click to expand...
Click to collapse
I believe you gotta wait for like 360 hours or something
Is it possible to have a complete translation ? Thanks
Have you tried to install magisk using this recovery?
ribou said:
Is it possible to have a complete translation ? Thanks
Click to expand...
Click to collapse
What do you mean a complete translation.
ZoneDev said:
Have you tried to install magisk using this recovery?
Click to expand...
Click to collapse
Yeah I do. But you'll need to reflash it after a few reboot.
seanho12345 said:
Yeah I do. But you'll need to reflash it after a few reboot.
Click to expand...
Click to collapse
Any ways for it to be flashed onced permanently?
ZoneDev said:
Any ways for it to be flashed onced permanently?
Click to expand...
Click to collapse
I don't think so.
seanho12345 said:
I don't think so.
Click to expand...
Click to collapse
I installed lazyflasher and the twrp recovery didnt got replaced
ZoneDev said:
I installed lazyflasher and the twrp recovery didnt got replaced
Click to expand...
Click to collapse
What do you mean. This twrp itself can decrypt data.
There's no need to flash lazyflasher.
seanho12345 said:
I don't think so.
Click to expand...
Click to collapse
Really? Are you trying to say that root is always temporary and after a few reboots we will always have to enter recovery to re-install Magisk? What about SuperSU?
Does anybody know the reason for this replacement? Maybe this will help us figure out how to prevent Magisk from being overwritten...
Thanks for this recovery.
But, at every boot I have this message “Android System there's an internal problem with your device.Contact your manufactirer for details.".
How to delete it.
It is possible to relock bootloader ?
Che0063 said:
Really? Are you trying to say that root is always temporary and after a few reboots we will always have to enter recovery to re-install Magisk? What about SuperSU?
Does anybody know the reason for this replacement? Maybe this will help us figure out how to prevent Magisk from being overwritten...
Click to expand...
Click to collapse
I Not 100% shure, but I think I'm loosing magisk root whenever I Update any systemapp..
Help me guys so i have my phone rooted via patched boot.img provided by Magisk but then decided to grab my stock boot.img to patch it again so i can update to v22.0 then i restart my device to access for fastboot and everything went blackscreen(i can't even see anything literally) luckily for me i memorize the key command to access fastboot so i flashed my stock boot.img , recovery.img and vendor.img but now my phone won't start
This thing shows up
https://imgur.com/a/fVDp06e
yes it's provably stupid to flash stock boot.img , recovery.img and vendor.img but i panic everything went all black even the BLU logo is black (no backlight phone)
What phone do you have? I think one way to try is to flash the boot.img, then boot into recovery from adb and try instaling full android from there. I haven't tried this yet but in a few hours I just might
Oliie23 said:
What phone do you have? I think one way to try is to flash the boot.img, then boot into recovery from adb and try instaling full android from there. I haven't tried this yet but in a few hours I just might
Click to expand...
Click to collapse
well that escalated quickly i just want fully update Magisk now i need to install full stock rom
ineedroot69 said:
well that escalated quickly i just want fully update Magisk now i need to install full stock rom
Click to expand...
Click to collapse
If I'm thinking correctly you won't lose data. Just dirtyflash it and it should work fine
Update ::
I flashed my stock system.img via fastboot and it fuking fix the issue
and would you look at that good as new
i thought Magisk is systemless but somehow my system.img got corrupted
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ineedroot69 said:
Update ::
I flashed my stock system.img via fastboot and it fuking fix the issue
and would you look at that good as new
i thought Magisk is systemless but somehow my system.img got corrupted
Click to expand...
Click to collapse
Great news. So how did you obtain the system.img? Did you flash just that and it booted? Do you have a custom recovery?
Oliie23 said:
Great news. So how did you obtain the system.img? Did you flash just that and it booted? Do you have a custom recovery?
Click to expand...
Click to collapse
no i don't have custom recovery like TWRP the development for my device is quite dead
also i use this thread https://forum.xda-developers.com/t/amazing-temp-root-for-mediatek-armv8-2020-08-24.3922213/ to dump all my device partition just in case something like this happen
ahh it fixed now my mother won't kill me
ineedroot69 said:
no i don't have custom recovery like TWRP the development for my device is quite dead
also i use this thread https://forum.xda-developers.com/t/amazing-temp-root-for-mediatek-armv8-2020-08-24.3922213/ to dump all my device partition just in case something like this happen
Click to expand...
Click to collapse
Did you lose data? And have you dumped the files before and that's how you've had the system.img?
Oliie23 said:
Did you lose data? And have you dumped the files before and that's how you've had the system.img?
Click to expand...
Click to collapse
look like completely factory default the bloatware are back
Just tried the update - completely messed up the phone - bootlooping, unable to flash a prev vers of magisk - doing a dirty flash....
Sebi673 said:
Just tried the update - completely messed up the phone - bootlooping, unable to flash a prev vers of magisk - doing a dirty flash....
Click to expand...
Click to collapse
ahaha this Magisk update v22.0 is bonker
Sebi673 said:
Just tried the update - completely messed up the phone - bootlooping, unable to flash a prev vers of magisk - doing a dirty flash....
Click to expand...
Click to collapse
Let me know how it goes, please
ineedroot69 said:
look like completely factory default the bloatware are back
Click to expand...
Click to collapse
Are your apps all gone? It's basically like clean flash, right?
Oliie23 said:
Let me know how it goes, please
Click to expand...
Click to collapse
dirty flash worked, reinstalled prev magisk v. magisk hide got stuck and did not complete with custom name, yet after a restart it asked to dl something something and worked - banking app does not see magisk. will stick to the prev magisk v
Sebi673 said:
dirty flash worked, reinstalled prev magisk v. magisk hide got stuck and did not complete with custom name, yet after a restart it asked to dl something something and worked - banking app does not see magisk. will stick to the prev magisk v
Click to expand...
Click to collapse
Wonderful news. So in your case it would stay in Fastboot and wouldn't launch? What did you do then?
Oliie23 said:
Wonderful news. So in your case it would stay in Fastboot and wouldn't launch? What did you do then?
Click to expand...
Click to collapse
tried flashing the new version via twrp but i was met by an error right after unpacking. At that point i couldn't save the logs sadly.
followed by device corruption warn on boot w/ the usual bootloop.
twrp, fastboot and flashmode were ok but simply flashing the boot img didn't work - had to do a full sys flash and then magisk.
[updatee] screens attached
Sebi673 said:
tried flashing the new version via twrp but i was met by an error right after unpacking. At that point i couldn't save the logs sadly.
followed by device corruption warn on boot w/ the usual bootloop.
twrp, fastboot and flashmode were ok but simply flashing the boot img didn't work - had to do a full sys flash and then magisk.
Click to expand...
Click to collapse
Mine won't go into TWRP from the Fastboot unfortunately. It just stays there. I've managed to get TWRP to launch from ADB but I'm not sure if I should just flash the ROM that way. Should I?
[duplicate]