I was trying to install twrp and root, and somehow mess up partition A. When i boot the phone on partition A, im getting stuck at the android one boot screen. When i boot in partition B i'm in twrp recovery. Question: How to get the stock partition A back?
xxtra_strength said:
I was trying to install twrp and root, and somehow mess up partition A. When i boot the phone on partition A, im getting stuck at the android one boot screen. When i boot in partition B i'm in twrp recovery. Question: How to get the stock partition A back?
Click to expand...
Click to collapse
Flash stock boot.img to boot_a
https://sourceforge.net/projects/others/files/MiA2/
Nebrassy said:
Flash stock boot.img to boot_a
https://sourceforge.net/projects/others/files/MiA2/
Click to expand...
Click to collapse
Thanks Lattakia, i was able to get my phone to boot up.
Nebrassy said:
Flash stock boot.img to boot_a
https://sourceforge.net/projects/others/files/MiA2/
Click to expand...
Click to collapse
How can i get stock recovery back on partition A?
xxtra_strength said:
How can i get stock recovery back on partition A?
Click to expand...
Click to collapse
You quoted the answer of your question
Nebrassy said:
You quoted the answer of your question
Click to expand...
Click to collapse
I was using the wrong flash command to load back stock. i have it now, and thanks again.
Related
Hi guys!
So i unlocked my m7 and though i could flash a twrp custom recovery.
But somehow the phone stuck on fastboot usb when i boot to recovery via cmd command promp...
I got :
C:\xxxxxxxxx\mini-sdk>fastboot boot twrp-3.0.0-2-m7.img
downloading 'boot.img'... OKAY
booting... OKAY
But the phone won t boot to recovery.
The vol up/down doesn t work either so i had to use power button to shut down my phone..
Tried many times but it didn t work.
Somebody knows why is that ?
nARDOs said:
Hi guys!
So i unlocked my m7 and though i could flash a twrp custom recovery.
But somehow the phone stuck on fastboot usb when i boot to recovery via cmd command promp...
I got :
C:\xxxxxxxxx\mini-sdk>fastboot boot twrp-3.0.0-2-m7.img
downloading 'boot.img'... OKAY
booting... OKAY
But the phone won t boot to recovery.
The vol up/down doesn t work either so i had to use power button to shut down my phone..
Tried many times but it didn t work.
Somebody knows why is that ?
Click to expand...
Click to collapse
The "fastboot boot recovery.img" is not supported in hboot 1.54 to 1.61 (was only supported in 1.44). So you can't boot a recovery you must flash it over your stock recovery using "fastboot flash recovery twrp-3.0.0-2-m7.img":
Code:
fastboot flash recovery twrp-3.0.0-2-m7.img
fastboot erase cache
fastboot reboot-bootloader
Then reboot in recovery mode.
alray said:
The "fastboot boot recovery.img" is not supported in hboot 1.54 to 1.61 (was only supported in 1.44). So you can't boot a recovery you must flash it over your stock recovery using "fastboot flash recovery twrp-3.0.0-2-m7.img":
Code:
fastboot flash recovery twrp-3.0.0-2-m7.img
fastboot erase cache
fastboot reboot-bootloader
Then reboot in recovery mode.
Click to expand...
Click to collapse
Thanks
Got custom recovery.
Just need to find a stock recovery next time :good:
Another question: is the nandroid backup size that big ? it said 6504 MB and i have only about 2700MB available..
Need to free some space...........
nARDOs said:
Thanks
Got custom recovery.
Just need to find a stock recovery next time :good:
Another question: is the nandroid backup size that big ? it said 6504 MB and i have only about 2700MB available..
Need to free some space...........
Click to expand...
Click to collapse
Nandroid backup of? It depends what is included in the backup.... if the data partition is included and there were a lot of things saved on the phone then yes it can be really big.... Normally id say around 1.5 gb is normal when its a stock backup without any user data.
alray said:
Nandroid backup of? It depends what is included in the backup.... if the data partition is included and there were a lot of things saved on the phone then yes it can be really big.... Normally id say around 1.5 gb is normal when its a stock backup without any user data.
Click to expand...
Click to collapse
Was actually thinking of stock backup without user data.
Do i have to backup "Boot" also ? or only the "system".
nARDOs said:
Was actually thinking of stock backup without user data.
Do i have to backup "Boot" also ? or only the "system".
Click to expand...
Click to collapse
Boot is the kernel and system is the OS. I would recommend to backup both of them. Boot isn't very big so it worth being backed up.
Sent from my HTC One using XDA Labs
alray said:
Boot is the kernel and system is the OS. I would recommend to backup both of them. Boot isn't very big so it worth being backed up.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
OK.
Is the Root feature on TWRP stable ? Can i use it to root ?
alray said:
Boot is the kernel and system is the OS. I would recommend to backup both of them. Boot isn't very big so it worth being backed up.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Hi again,
Can I find stock recovery.img on the nandroid file ?
Didn t find it t there.
nARDOs said:
OK.
Is the Root feature on TWRP stable ? Can i use it to root ?
Click to expand...
Click to collapse
If you are going to use twrp's root make sure you have a recent twrp version otherwise it will flash an outdated SU version and cause a Bootloop. But yes it's a reliable method, if you prefer you can flash the latest supersu.zip file from twrp.
nARDOs said:
Hi again,
Can I find stock recovery.img on the nandroid file ?
Didn t find it t there.
Click to expand...
Click to collapse
Stock recovery isn't included in a nandroid. What is your version-main number? Will try to find it for you.
Sent from my HTC One using XDA Labs
alray said:
If you are going to use twrp's root make sure you have a recent twrp version otherwise it will flash an outdated SU version and cause a Bootloop. But yes it's a reliable method, if you prefer you can flash the latest supersu.zip file from twrp.
Stock recovery isn't included in a nandroid. What is your version-main number? Will try to find it for you.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Thanks mate.
Mine is 7.19.401.51.
nARDOs said:
Thanks mate.
Mine is 7.19.401.51.
Click to expand...
Click to collapse
yep make sure to use SuperSu 2.65
https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
alray said:
yep make sure to use SuperSu 2.65
https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
Click to expand...
Click to collapse
Thanks :good:
Do u know a better custom ROM which is not based on sense ?
I m thinking about miui v6 (don t know if there is stable miui v7 for m7) or cm12 (or stable cm13)
I was running Freedom OS CE 2.5 and I dirty flashed official OOS 4.1.0 and got into a bootloop.
I restarted the phone into twrp and it told me that it was read only so I wasn't seeing any zip files. I tried to use repair in the Wipe section by changing file format. I think I chose FAT...I honestly can't remember. But when I swipe to repair and I got stock on updating partition. So I restarted the device into twrp again but this time I'm stock on just the splash screen....won't start.
All I'm getting into is bootloader mode.
Help please
Use fastboot to wipe recovery and flash TWRP again. Alternatively, directly sideload your ROM.
Anova's Origin said:
Use fastboot to wipe recovery and flash TWRP again. Alternatively, directly sideload your ROM.
Click to expand...
Click to collapse
Thank you so much. But what about how I tried changing the format from what it was originally? Should I be worried or that's a minor issue?
ddaharu said:
Thank you so much. But what about how I tried changing the format from what it was originally? Should I be worried or that's a minor issue?
Click to expand...
Click to collapse
You should reformat those partitions that you've changed. Ext4 or f2fs for /data and ext4 for all other partitions. This can be done through either fastboot or TWRP.
Anova's Origin said:
You should reformat those partitions that you've changed. Ext4 or f2fs for /data and ext4 for all other partitions. This can be done through either fastboot or TWRP.
Click to expand...
Click to collapse
Are these the commands I should use?
c:\adb>fastboot erase recovery
c:\adb>fastboot flash recovery twrp
Well as you said, after this I can reenter recovery and reformat the partitions and I should be fine right?
Thanks for all your help man...
ddaharu said:
Are these the commands I should use?
c:\adb>fastboot erase recovery
c:\adb>fastboot flash recovery twrp
Well as you said, after this I can reenter recovery and reformat the partitions and I should be fine right?
Thanks for all your help man...
Click to expand...
Click to collapse
Dont forget the ".img" when referring to images"
c:\adb>fastboot flash recovery twrp.img
Anova's Origin said:
Dont forget the ".img" when referring to images"
c:\adb>fastboot flash recovery twrp.img
Click to expand...
Click to collapse
One last question. Is there any twrp version you'll recommend? Or anyone is good?
ddaharu said:
One last question. Is there any twrp version you'll recommend? Or anyone is good?
Click to expand...
Click to collapse
3.0.4-1 has proven to be the most stable so far.
I've also been using 3.1.0-1 for a while and haven't noticed any issues.
Avoid 3.1.0.0 though, as there has been many reports of issues with it.
Anova's Origin said:
3.0.4-1 has proven to be the most stable so far.
I've also been using 3.1.0-1 for a while and haven't noticed any issues.
Avoid 3.1.0.0 though, as there has been many reports of issues with it.
Click to expand...
Click to collapse
MY PHONE IS RUNNING AGAIN! thanks for your help man.
Btw! Seeing that the positions were somewhat corrupted, I actually had to use stock recovery to sideload the stock ROM then flash TWRP and finally on freedom is 2.6.1
Thanks again, mate. :highfive:
ddaharu said:
I was running Freedom OS CE 2.5 and I dirty flashed official OOS 4.1.0 and got into a bootloop.
I restarted the phone into twrp and it told me that it was read only so I wasn't seeing any zip files. I tried to use repair in the Wipe section by changing file format. I think I chose FAT...I honestly can't remember. But when I swipe to repair and I got stock on updating partition. So I restarted the device into twrp again but this time I'm stock on just the splash screen....won't start.
All I'm getting into is bootloader mode.
Help please
Click to expand...
Click to collapse
I faced a similar issue with twrp , just try to flash twrp again using fastboot mode , in case it does not work again then try to flash it a few more times , it would surely work , I have already tried it , but before that try to factory reset ur phone using twrp and reboot to twrp and only use the first method if the problem exists after that
9891ishu said:
I faced a similar issue with twrp , just try to flash twrp again using fastboot mode , in case it does not work again then try to flash it a few more times , it would surely work , I have already tried it , but before that try to factory reset ur phone using twrp and reboot to twrp and only use the first method if the problem exists after that
Click to expand...
Click to collapse
Thanks. I got through.
Hello
I flashed lineage os a while ago on my K013 but now i want to rollback to the original ROM
Any ideas how to roll back
Thanks in advanced
Flash the stock ROM in your recovery: http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36-user.zip
Before you boot, make sure you do a full factory reset. Also if you have been using F2FS for cache/data partitions you will need to reformat them to ext4, the stock ROM doesn't support f2fs. Otherwise your device won't boot correctly.
lambdadroid said:
Flash the stock ROM in your recovery: http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36-user.zip
Before you boot, make sure you do a full factory reset. Also if you have been using F2FS for cache/data partitions you will need to reformat them to ext4, the stock ROM doesn't support f2fs. Otherwise your device won't boot correctly.
Click to expand...
Click to collapse
my device is now bricked because i tried this and it's stock at intel logo what will i do now
Ahmadboustani said:
my device is now bricked because i tried this and it's stock at intel logo what will i do now
Click to expand...
Click to collapse
Can you still boot into recovery? I can only guess that you didn't do a proper factory reset.
lambdadroid said:
Can you still boot into recovery? I can only guess that you didn't do a proper factory reset.
Click to expand...
Click to collapse
no i can't what should i do
Ahmadboustani said:
no i can't what should i do
Click to expand...
Click to collapse
Can you try the steps explained in "Troubleshooting -> Recovery" in this thread: https://forum.xda-developers.com/me...otloader-me176c-boot-asus-memo-pad-7-t3780225
That should allow you to boot into Fastboot and Recovery.
lambdadroid said:
Can you try the steps explained in "Troubleshooting -> Recovery" in this thread: https://forum.xda-developers.com/me...otloader-me176c-boot-asus-memo-pad-7-t3780225
That should allow you to boot into Fastboot and Recovery.
Click to expand...
Click to collapse
ok im able to go to bootloader now but when i flash the stock rom through twrp it gives me error : 7 and won't flash
what should i do now
Ahmadboustani said:
ok im able to go to bootloader now but when i flash the stock rom through twrp it gives me error : 7 and won't flash
what should i do now
Click to expand...
Click to collapse
Hmm, not sure what's going on there. Can you post a picture of the full error?
Hi. I'm also k013 user, same problem. Stuck on fastboot starting ... Fastboot starting ...#1 fastboot starting ...#2 fastboot starting ...#3.
I also tried "fastboot boot droidboot.img" in cmd but my k013 reboot back into fastboot starting ... Fastboot starting ...#1 fastboot starting ...#2 fastboot starting ...#3.
Can you help me in this?
Tia
Trying to sideload the December OTA. Rooted with Magisk. Boot into bootloader, select recovery, then I get the google logo (not the red exclamation mark, the Google logo) , but won't enter recovery, just hangs on the logo. Do I need to disable or uninstall Magisk?
Gloff said:
Trying to sideload the December OTA. Rooted with Magisk. Boot into bootloader, select recovery, then I get the google logo (not the red exclamation mark, the Google logo) , but won't enter recovery, just hangs on the logo. Do I need to disable or uninstall Magisk?
Click to expand...
Click to collapse
You need to uninstall magisk and then enable the stock boot.img which is where the recovery resides.
Badger50 said:
You need to uninstall magisk and then enable the stock boot.img which is where the recovery resides.
Click to expand...
Click to collapse
That's new, didn't have to do that with the 3 XL. Do I use the stock boot.img from the currently installed update (december)? Also, how to I flash the stock boot.img, through fastboot?
Gloff said:
That's new, didn't have to do that with the 3 XL. Do I use the stock boot.img from the currently installed update (december)? Also, how to I flash the stock boot.img, through fastboot?
Click to expand...
Click to collapse
Although I never do OTA's, I prefer fastbooting updates, most everything I've read is to uninstall magisk, then restore the stock boot.img which magisk will do for you. So it's either that is causing his problem, or he has an issue with his stock recovery.
Badger50 said:
Although I never do OTA's, I prefer fastbooting updates, most everything I've read is to uninstall magisk, then restore the stock boot.img which magisk will do for you. So it's either that is causing his problem, or he has an issue with his stock recovery.
Click to expand...
Click to collapse
You're talking to the OP. I couldn't update Magisk with the last update, it said installation failed. Should I just flash the stock boot.img?
Gloff said:
You're talking to the OP. I couldn't update Magisk with the last update, it said installation failed. Should I just flash the stock boot.img?
Click to expand...
Click to collapse
Yes
p70shooter said:
Yes
Click to expand...
Click to collapse
I assume the boot.img from December Update, yes?
Gloff said:
I assume the boot.img from December Update, yes?
Click to expand...
Click to collapse
Yes. fastboot flash boot boot.img :good:
Gloff said:
I assume the boot.img from December Update, yes?
Click to expand...
Click to collapse
Yea if you're flashing that one. I would just flash the whole December image using flash all, saves messing around with Ota then but that's me
p70shooter said:
Yea if you're flashing that one. I would just flash the whole December image using flash all, saves messing around with Ota then but that's me
Click to expand...
Click to collapse
I was always worried about wiping my devices, that's why I usually sideload the OTA rather than removing the -w flag.
Gloff said:
I was always worried about wiping my devices, that's why I usually sideload the OTA rather than removing the -w flag.
Click to expand...
Click to collapse
Ah that makes sense, I always double or triple check that I've removed the -w but I have forgotten before lol
p70shooter said:
Ah that makes sense, I always double or triple check that I've removed the -w but I have forgotten before lol
Click to expand...
Click to collapse
Hahahahahaha....I think I remember a couple of those! ?
The Guide should be updated for flashing both slots, I've never been able to get fastboot flash boot --slot all boot.img to work, so I've always flashed both slots individually using
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Is there a new command for flashing both slots simultaneously?
So when updating, do you guys just flash the entire updated factory image when a new update is released? No need to uninstall Magisk, so you don't have to flash the previous update's boot.img?
In other words do you flash new full factory image>patch boot.img>flash magisk_patched> done VS.
Flash old stock boot.img>OTA/Factory image>patch boot.img>flash magisk_patched>done?
This has never been clear to me as far as new updates go. I feel like the guide should have an "I'm rooted and just want to update to the latest security patch" section.
Gloff said:
The Guide should be updated for flashing both slots, I've never been able to get fastboot flash boot --slot all boot.img to work, so I've always flashed both slots individually using
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Is there a new command for flashing both slots simultaneously?
Click to expand...
Click to collapse
Might try this one. Always seems to work for me :good:
fastboot flash boot boot.img --slot=all
Then substitute magisk_patched.img for boot.img when you want to flash the rooted version of the kernel to both slots :good:
Badger50 said:
Might try this one. Always seems to work for me :good:
fastboot flash boot boot.img --slot=all
Then substitute magisk_patched.img for boot.img when you want to flash the rooted version of the kernel to both slots :good:
Click to expand...
Click to collapse
Will try this command after I finish updating to January. Who wrote the guide? They have it as: fastboot flash boot --slot all magisk_patched.img.
They should update it if the order is backwards, since it's never worked for me using the guide's script.
Edit: fastboot flash boot boot.img --slot=all did not work either. I used the boot_a/boot_ b method and it worked fine.
Gloff said:
Will try this command after I finish updating to January. Who wrote the guide? They have it as: fastboot flash boot --slot all magisk_patched.img.
They should update it if the order is backwards, since it's never worked for me using the guide's script.
Click to expand...
Click to collapse
There are few guides, depends on which one your referring too. It's actually not backwards as either will work. Probably just a syntax error or typo :good:
Badger50 said:
There are few guides, depends on which one your referring too. It's actually not backwards as either will work. Probably just a syntax error or typo :good:
Click to expand...
Click to collapse
This Guide: https://forum.xda-developers.com/pixel-4-xl/how-to/guide-pixel-4-xl-android-10-q-root-t3996969
I attached my command window log.
Gloff said:
This Guide: https://forum.xda-developers.com/pixel-4-xl/how-to/guide-pixel-4-xl-android-10-q-root-t3996969
I attached my command window log.
Click to expand...
Click to collapse
Maybe try the = sign between slot and all
Looks like the one I gave you works though :good:
Badger50 said:
Maybe try the = sign between slot and all
Looks like the one I gave you works though :good:
Click to expand...
Click to collapse
Tried that, middle of the attachment results in fastboot: unknonw option --slot=all
Pre rooted boot image with TWRP included for OOS11 Beta 2, OB2. This is not for the beta 1 hotfix. Flash in fastboot if not rooted, and through a kernel manager if you are already on beta 2 and rooted but don't have TWRP because flashing kept putting you in crash dump mode. Remove lock screen as a precaution before flash. No need to wipe anything.
Just like any other image I tried, this gets me into a boot loop on the spinning circle. I can get into twrp, but the magisk root seems to be breaking something. Any ideas?
romanuks said:
Just like any other image I tried, this gets me into a boot loop on the spinning circle. I can get into twrp, but the magisk root seems to be breaking something. Any ideas?
Click to expand...
Click to collapse
What device are you using ( 6 or 6T ) ? Or whats the code name for your device??
SOK seila said:
What device are you using ( 6 or 6T ) ? Or whats the code name for your device??
Click to expand...
Click to collapse
OP6T europe
i use command "fastboot boot fajita-ob2-oos11-twrp-rooted.img" but in boot to system
lockmunk said:
i use command "fastboot boot fajita-ob2-oos11-twrp-rooted.img" but in boot to system
Click to expand...
Click to collapse
you should probably write fastboot flash boot ...
romanuks said:
you should probably write fastboot flash boot ...
Click to expand...
Click to collapse
"fastboot boot" and "fastboot flash" are do the same thing (to flash). If you use "fastboot flash" you have to manually reboot the phone to system or twrp, it is auto reboot after finished flash (based on image if flash TWRP it will boot to TWRP) if you use "fastboot boot".
Sooooo, any ideas on what I could do?
romanuks said:
Sooooo, any ideas on what I could do?
Click to expand...
Click to collapse
So you are using op6T-EU. I don't know if eu image different from groble image or not but you can try to patch boot image yourself.
Well, I already tried that too, so really not a clue as to why it wouldnt work... Probably should just downgrade, backup and get lineage or so