Related
please..
i have problem with bootloader version 41.1A
i want to Downgrade to version 41.18 or 41.19
anyone know ..??
please share it
thank you
Up
Me too
My bootloader v 41.1A I downgrade 41.18 Help
Why do you need to downgrade? Messing with Bootloaders can destroy your phone.
even i want to downgrade... I cant flash custom recovery on 41.1A
poran123 said:
even i want to downgrade... I cant flash custom recovery on 41.1A
Click to expand...
Click to collapse
Bootloader cannot be downgraded. You're stuck on w/e version you have currently installed.
Okay so I'm stuck on 41.1A and my phone will continue to restart itself and then stuck in bootloop till the battery dies... and then when I connect it to the charger boot's up normally...
@lost101
Can you please let me know how to check bootloader version?
I am using Moto G XT1033 model(Asia).
It was updated to Lollipop 5.0.2 by Motorola Stock Lollipop update.
Later on I had unlocked bootloader and downgraded it to Kitkat 4.4.4 using this thread.
I don't have any clue about current version of bootloader in my Moto G.
I want to try Lollipop 5.1 Optimized stock rom link here, so just wanted to ensure compatibility of bootloader so that my phone works after flashing it.
kalpesh.fulpagare said:
@lost101
Can you please let me know how to check bootloader version?
Click to expand...
Click to collapse
Enter bootloader (hold volume-down while turning it on), read text on screen (second line).
I too want to know if there is a way to downgrade or at least reflash my damaged bootloader which is causing weird behaviour.
Sent from my Nexus 6P using Tapatalk
I have the exact same problem.
Stuck on 41.1A
Was on a slim6 rom before. Tried to return to STOCK_ASIA_RETAIL. All fastboot commands successfully executed but no apparent change. I have the exact same wallpaper, the same layers RRO navbars, everything. I would not need to go to STOCK but since the slim installation is unstable and everything force closes, the phone is unusable.
Additional note: Somehow even TWRP is stuck in the splash screen, so cant flash any other ROM. Even tried to access TWRP using adb, but the TWRP service fails to start.
I fastboot flashed phillz recovery, stock recovery & newer TWRP versions, but nothing happens. Phone still stuck in TWRP screen.
To my surprise I was able to pull my personal files from the internal SD using ADB (which still works btw).
But I'm left with a phone in a zombie unusable condition, it just doesn't react to anything.
Any help from the XDA community would be greatly appreciated. I am still keeping my fingers crossed, so that one day a guide comes up to brick my device (STOCK 5.1 bootloader) and unbrick it using some sort of unbrick tool.
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
SLATE21&MOTOG said:
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
Click to expand...
Click to collapse
Creating such a zip is possible, but flashing it may either not work or hard brick your phone.
How to install working recovery on 41.1A bootloader
I had the situation on my Moto G XT1039 where I had formatted the partitions on my phone (using my old CWM recovery), then flashed the 41.1A bootloader, but 41.1A would not allow me to flash any recovery.
So I had a working bootloader, but no recovery and no OS. And apparently no way to install a recovery, to install an OS...
I got the phone back like this:
- Flashed 4.4.4 stock manually using the bootloader (if you do this, DO NOT flash the 4.4.4 motoboot.img, according to everything on here that will permanently brick your phone; I am not sure about partition gpt.bin - I flashed this, but I was already on the 4.4.4 partition layout anyway). Do flash boot.img, that is the OS boot.
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
From there I now had the correct recovery in place to flash the 5.1 Optimized distro (which I would definitely recommend - clean, stable, excellent battery life!).
Yay!
Bmju said:
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
Click to expand...
Click to collapse
Why didn't you simply fastboot flash a TWRP image?
_that said:
Why didn't you simply fastboot flash a TWRP image?
Click to expand...
Click to collapse
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Bmju said:
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Click to expand...
Click to collapse
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
_that said:
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
Click to expand...
Click to collapse
Thanks! I definitely tried that first! Maybe this bit I didn't make clear in my post, but actually:
- fastboot boot was only working for me with older recovery ROMS, i.e. the older CWM recovery which I mentioned, which I had lying around from when I first rooted my phone on 4.4.4, and also - not that it's much use - with the recovery in the 4.4.4 image, which just brings up the dead Android logo
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Bmju said:
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
Click to expand...
Click to collapse
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Bmju said:
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
Click to expand...
Click to collapse
That doesn't make any sense. Not that I don't believe you, I just can't explain how fastboot could fail writing recovery but succeed in writing a different partition.
Bmju said:
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Click to expand...
Click to collapse
Thanks for sharing your experience though, maybe it will help someone who has the same weird issue.
_that said:
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Click to expand...
Click to collapse
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Bmju said:
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Click to expand...
Click to collapse
Yes, I've got that one too, but my flashed recovery then worked fine. However I upgraded my bootloader by installing the complete 5.1 stock ROM, maybe your bootloader update was somehow incomplete.
HTCDreamOn said:
A word of advice: I strongly recommend temporarily booting any images (be it recoveries or kernels) you are about to flash to your device. This is simply a case of using the command "fastboot boot blahblah.img" whether blahblah.img is a recovery or kernel.
Click to expand...
Click to collapse
We know you can boot to TWRP vice flash to your device by using the command:
Code:
fastboot boot twrp.img
But how do you proceed from here? Are you required to use ADB commands at this point or can you unplug your USB cable and use TWRP as if it was installed, I.E. , back up current ROM, and install new zip.
purplepizza said:
We know you can boot to TWRP vice flash to your device by using the command:
Code:
fastboot boot twrp.img
But how do you proceed from here? Are you required to use ADB commands at this point or can you unplug your USB cable and use TWRP as if it was installed, I.E. , back up current ROM, and install new zip.
Click to expand...
Click to collapse
Sorry if I wasn't clear. Yes you can unplug usb and use as normal, it just means twrp isn't flashed to the device so it won't be there when you reboot.
I just recommend this step because I'm paranoid. Once you've confirmed the image works you should reboot to bootloader and fastboot flash the image, then you'll be able to boot into twrp whenever you want.
HTCDreamOn said:
Sorry if I wasn't clear. Yes you can unplug usb and use as normal, it just means twrp isn't flashed to the device so it won't be there when you reboot.
I just recommend this step because I'm paranoid. Once you've confirmed the image works you should reboot to bootloader and fastboot flash the image, then you'll be able to boot into twrp whenever you want.
Click to expand...
Click to collapse
This is a good step to do, and if the device supports it it should be used... for example the Moto G (if unlocked) fully supports fastboot boot commands, devices like the HTC One M7 do NOT support this anymore...
To the OP, what is really happening here is that TWRP or the boot.img (kernel) is being loaded from USB into RAM and executed normally, instead of the standard /boot partition which is skipped when executing fastboot boot. TWRP (and recovery in general) is really just a specialized micro-sized android distribution and when started via fastboot boot is executed as if it was the boot image. Once the image is transferred into RAM, the boot continues normally per the instructions of TWRP or the boot image, and no further action via USB is required. USB is just the medium to load the image into RAM and nothing more.
fastboot boot - used to manually load a boot image (or recovery) and execute from RAM, it is not flashed to the device, on the next reboot it will return to it's previous state
fastboot flash boot/recovery - used to actually flash the boot image or recovery image to the it's appropriate partition on the device, it does not execute it. On a reboot or factory default this information will stay in the device.
acejavelin said:
This is a good step to do, and if the device supports it it should be used... for example the Moto G (if unlocked) fully supports fastboot boot commands, devices like the HTC One M7 do NOT support this anymore...
To the OP, what is really happening here is that TWRP or the boot.img (kernel) is being loaded from USB into RAM and executed normally, instead of the standard /boot partition which is skipped when executing fastboot boot. TWRP (and recovery in general) is really just a specialized micro-sized android distribution and when started via fastboot boot is executed as if it was the boot image. Once the image is transferred into RAM, the boot continues normally per the instructions of TWRP or the boot image, and no further action via USB is required. USB is just the medium to load the image into RAM and nothing more.
fastboot boot - used to manually load a boot image (or recovery) and execute from RAM, it is not flashed to the device, on the next reboot it will return to it's previous state
fastboot flash boot/recovery - used to actually flash the boot image or recovery image to the it's appropriate partition on the device, it does not execute it. On a reboot or factory default this information will stay in the device.
Click to expand...
Click to collapse
Thanks. So it seems there is no reason to ever flash TWRP unless you don't want the PC dependence to use the TWRP tool.
purplepizza said:
Thanks. So it seems there is no reason to ever flash TWRP unless you don't want the PC dependence to use the TWRP tool.
Click to expand...
Click to collapse
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
acejavelin said:
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
Click to expand...
Click to collapse
I understand what you are saying. The only flash I planned on was SuperSU. I thought when a system upgrade is available, I could simply use SU to unroot and be ready for the update. Would this work?
If I followed your recommendation, could I feasibly, flash TWRP, then when an upgrade is ready, flash nandroid backup (which I assume removes TWRP) then accept system update, then re-flash TWRP. I could restore apps by using TB. Does this make sense? Or does TWRP remain in place after flashing nandroid backup?
purplepizza said:
I understand what you are saying. The only flash I planned on was SuperSU. I thought when a system upgrade is available, I could simply use SU to unroot and be ready for the update. Would this work?
If I followed your recommendation, could I feasibly, flash TWRP, then when an upgrade is ready, flash nandroid backup (which I assume removes TWRP) then accept system update, then re-flash TWRP. I could restore apps by using TB. Does this make sense? Or does TWRP remain in place after flashing nandroid backup?
Click to expand...
Click to collapse
TWRP remains in place after restoring a nandroid (I think, I haven't installed on my Moto G, but in most devices it doesn't backup/restore recovery), but you can easily restore the original recovery via fastboot.
acejavelin said:
TWRP remains in place after restoring a nandroid (I think, I haven't installed on my Moto G, but in most devices it doesn't backup/restore recovery), but you can easily restore the original recovery via fastboot.
Click to expand...
Click to collapse
Just curious, how did you go from 5.1.1 to 6.0?
purplepizza said:
Just curious, how did you go from 5.1.1 to 6.0?
Click to expand...
Click to collapse
OTA... part of soak test on December 22.
acejavelin said:
OTA... part of soak test on December 22.
Click to expand...
Click to collapse
Hey thanks for helping to answer this, your explanation was much better I thought it had something to do with loading into RAM but wasn't sure. I didn't know some devices don't allow fastboot boot commands though, I've always relied on them. Part of the reason I'm avoiding htc now.
@purplepizza I agree with everything acejavelin has said: essentially you really do want to make sure your have twrp flashed.
To answer your nandroid question: It basically just takes an image of the partitions you choose, usually /system, /data, and /boot (where kernel stuff is) which is the least you need to boot back with all your data. It doesn't backup recovery and when you restore it doesn't write anything to recovery, so yes twrp will still be in place. In general you should only ever flash stuff to the recovery partition whilst in fastboot mode (i.e. using fastboot flash recovery recovery.img), I know on some devices you can flash recoveries as zip files in the recovery itself but you shouldn't.
I've seen quite a few people querying about the 6.0 OTA: in short, I wouldn't worry about it because once they start rolling out, people always catch the OTA and post here on xda. You can flash that and it'll return you to stock 6.0 anyway, at which point you can reroot and everything if you want.
acejavelin said:
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
Click to expand...
Click to collapse
One more question, when making the first nandroid backup. do you just back up system and data or do you include boot as well?
purplepizza said:
One more question, when making the first nandroid backup. do you just back up system and data or do you include boot as well?
Click to expand...
Click to collapse
My opinion is always backup everything, you can always choose what to restore
Sent from my MotoG3 using Tapatalk
acejavelin said:
My opinion is always backup everything, you can always choose what to restore
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
So what is boot? I know I am kind of going back to my previous question, but if I restore boot, is that the boot loader? I would assume this would not commonly need restored?
And I now assume the bootloader is completely independent from recovery.
purplepizza said:
So what is boot? I know I am kind of going back to my previous question, but if I restore boot, is that the boot loader? I would assume this would not commonly need restored?
And I now assume the bootloader is completely independent from recovery.
Click to expand...
Click to collapse
It is not the bootloader... It is the /boot partition of the phone, basically the kernel and RAM disk. If you screw things up and need to restore, you typically want to restore /boot, /system, and /data, and occasionally /cache (if you want to restore to save time and get an exact duplicate of the previous image, otherwise many people skip /cache and let it rebuild on the first boot which takes 10-15 minutes extra).
acejavelin said:
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
Click to expand...
Click to collapse
HTCDreamOn said:
@purplepizza I agree with everything acejavelin has said: essentially you really do want to make sure your have twrp flashed.
Click to expand...
Click to collapse
So I am following your advice. I booted to TWRP, made Nandroid backup.
Rebooted and flashed TWRP, see below:
Code:
sudo fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (7772 KB)...
OKAY [ 10.635s]
writing 'recovery'...
OKAY [ 0.141s]
finished. total time: 10.776s
All seems OK.
Scrolled to recovery, selected recovery. TWRP was there. I then powered down.
After that I held power and volume down, system boots to dead Android with message “No command” Held power then volume up, I see stock boot loader. Is TWRP flashed somewhere or is it gone? So what did I do wrong.
purplepizza said:
So I am following your advice. I booted to TWRP, made Nandroid backup.
Rebooted and flashed TWRP, see below:
Code:
sudo fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (7772 KB)...
OKAY [ 10.635s]
writing 'recovery'...
OKAY [ 0.141s]
finished. total time: 10.776s
All seems OK.
Scrolled to recovery, selected recovery. TWRP was there. I then powered down.
After that I held power and volume down, system boots to dead Android with message “No command” Held power then volume up, I see stock boot loader. Is TWRP flashed somewhere or is it gone? So what did I do wrong.
Click to expand...
Click to collapse
I have no idea, you did it right... selecting recovery from the bootloader should start TWRP, not stock recovery, that should be gone.
acejavelin said:
I have no idea, you did it right... selecting recovery from the bootloader should start TWRP, not stock recovery, that should be gone.
Click to expand...
Click to collapse
Any recommendations how to proceed?
I also need help with my soft bricked moto g3
Moto g3 (xt 1550, Indian dual sim 16 gb version)
I officially upgraded to 6.0.0 via ota and my objective was to root my phone and use xposed modules. I am not interested in any other custom rom (I'd rather keep stock rom just for moto display and ota upgrades) or custom recovery like twrp(I'm afraid it may cause ota upgrades to fail).
I used the method described here in the question- http://android.stackexchange.com/qu...rsu-using-play-store-versus-a-custom-recovery
So I first successfully unlocked my bootloader using the official motorola method.
I then proceeded to use google's backup settings to re-install all the apps that were uninstalled due to unlocking the bootloader. I also put supersu.zip version 2.46 on internal sd card.
I then proceeded to (without rebooting) enter fastboot where i used minimal adb to temporarily boot into twrp version2.8.7 r5 (link - http://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537 ).
Once in twrp, I located and flashed the supersu.zip. It flashed successfully. I procceded to clear dalvik cache and then after clearing cache I tried to reboot my phone using twrp.
However, it did not go beyond the "Warning - Bootloader Unlocked" screen that you get on unlocking a motorola bootloader. I left it for over 10 minutes (usb was still plugged in, I had >80% battery) but it did not proceed.
Long -pressing the power button causes the phone to vibrate and again attempt to boot, stuck at the same initial screen. Adb quite understandably does not work here.
I can press vol down+power and enter fastboot , where adb works fine.
I can enter stock recovery from the fastboot sceen too.
Using adb in fastboot, I am able to boot twrp . In fact, I tried to re-install supersu.zip. I retried version 2.46 and then tried version 2.56. On all occcassions, it was able to successfully flash it, but gets hung on the initial boot screen.
USB Debugging is also enabled, and I have a backp of my sd card data.
I tried taking a backup of the system and apps in twrp (3 gb in total) and tried to reflash it, but it still hangs at the same screen.
Is there any way I can unbrick my device and- (in decreasing order of preference)
1. Keep my stock rom and recovery?
2. Keep stock rom with twrp? (It should not be a problem)
3. Custom rom with custom recovery - perhaps official cm. Least preferred as I want Moto Display and stock/vanilla android.
Also, is SELinux involved anywhere with my phone getting bricked? I also read that a custom kernel is required for rooting 6.0, which I don't have. Supersu Version 2.56 is said to prevent soft bricks if the kernel is incorrect (systemless root), yet even after flashing the newer one it is still bricked. Where am I going wrong? What should I do? Thanks in advance! :good:
purplepizza said:
Any recommendations how to proceed?
Click to expand...
Click to collapse
Try the flash again? Sorry, but I don't really know help... if you are successfully rooted, perhaps try to flash TWRP image with Flashify? (select your file, don't let it auto-grab an image)
acejavelin said:
Try the flash again? Sorry, but I don't really know help... if you are successfully rooted, perhaps try to flash TWRP image with Flashify? (select your file, don't let it auto-grab an image)
Click to expand...
Click to collapse
I have not rooted yet. I guess I can try by booting TWRP then flashing SuperSU.
Can you think of any reasons not to try fastboot again the re-flash TWRP?
unlocked bootloader and installed twrp recovery with that I installed cyanogenmod 13 through it...after that I installed stock rom ....now when iam trying to install twrp recovery...it's showing no command....how to resolve it....
I searched about this issue in this forum but I didn't get the correct solution to solve the problem..
My device- Moto g3 xt1550
Android 6.0.1
vamshi151 said:
unlocked bootloader and installed twrp recovery with that I installed cyanogenmod 13 through it...after that I installed stock rom ....now when iam trying to install twrp recovery...it's showing no command....how to resolve it....
I searched about this issue in this forum but I didn't get the correct solution to solve the problem..
My device- Moto g3 xt1550
Android 6.0.1
Click to expand...
Click to collapse
I didnt get anything from the post. you have to be little bit specific.
i mean you
1. unlocked bootloader(fine)
2. installed twrp(also fine)
3. installed cm13(great)
4. you reverted back to stock rom??? How from twrp, flashfire or fastboot.?
and now how are you trying to install twrp? from fastboot?
Flash twrp image with fastboot, start TWRP, reboot recovery within TWRP, then twrp sticks... profit.
Arcade said:
I didnt get anything from the post. you have to be little bit specific.
i mean you
1. unlocked bootloader(fine)
2. installed twrp(also fine)
3. installed cm13(great)
4. you reverted back to stock rom??? How from twrp, flashfire or fastboot.?
and now how are you trying to install twrp? from fastboot?
Click to expand...
Click to collapse
From fastboot i installed stock rom then I try to install twrp again through fastboot mode but it's showing no command
which guide you used to flash stock rom through fastboot?
Motorola website
Arcade said:
I didnt get anything from the post. you have to be little bit specific.
i mean you
1. unlocked bootloader(fine)
2. installed twrp(also fine)
3. installed cm13(great)
4. you reverted back to stock rom??? How from twrp, flashfire or fastboot.?
and now how are you trying to install twrp? from fastboot?
Click to expand...
Click to collapse
What's the solution for that
Arcade said:
I didnt get anything from the post. you have to be little bit specific.
i mean you
1. unlocked bootloader(fine)
2. installed twrp(also fine)
3. installed cm13(great)
4. you reverted back to stock rom??? How from twrp, flashfire or fastboot.?
and now how are you trying to install twrp? from fastboot?
Click to expand...
Click to collapse
From fastboot i installed stock rom then I try to install twrp again through fastboot mode but it's showing no command
vamshi151 said:
From fastboot i installed stock rom then I try to install twrp again through fastboot mode but it's showing no command
Click to expand...
Click to collapse
TWRP is not sticking...
1) Start the bootloader, flash TWRP in fastboot with the command: fastboot flash recovery twrp.img (Replace twrp.img with the name of the TWRP img file)
2) Press VOL DN to start Recovery and select it, TWRP should start... When prompted if you should allow changes to system, say YES or allow or whatever so that is allowed to mount system as read-write.
3) In the TWRP main menu, select Reboot, then Reboot - Recovery
4) The device will restart and TWRP will start again, if asked to allow changed changes to system again, allow it
5) Go to Mounts and make sure Mount System Read-Only is NOT ticked
6) Press Home, then Reboot and Reboot Recovery again
TWRP will start again and be set, it will not go away unless you flash something with a recovery.img in the file (custom ROMs do not normally contain this file).
acejavelin said:
TWRP is not sticking...
1) Start the bootloader, flash TWRP in fastboot with the command: fastboot flash recovery twrp.img (Replace twrp.img with the name of the TWRP img file)
2) Press VOL DN to start Recovery and select it, TWRP should start... When prompted if you should allow changes to system, say YES or allow or whatever so that is allowed to mount system as read-write.
3) In the TWRP main menu, select Reboot, then Reboot - Recovery
4) The device will restart and TWRP will start again, if asked to allow changed changes to system again, allow it
5) Go to Mounts and make sure Mount System Read-Only is NOT ticked
6) Press Home, then Reboot and Reboot Recovery again
TWRP will start again and be set, it will not go away unless you flash something with a recovery.img in the file (custom ROMs do not normally contain this file).
Click to expand...
Click to collapse
Again It's showing no command
vamshi151 said:
Again It's showing no command
Click to expand...
Click to collapse
At what point? What command are you using to perform the flash?
I'm sorry... I've just done this on numerous G3's and what you are describing doesn't just happen for no reason... either the initial flash was done incorrectly, the process to set it was not followed, or there is actually a defect in the device (which is unlikely if TWRP boots even once after bring flashed).
vamshi151 said:
unlocked bootloader and installed twrp recovery with that I installed cyanogenmod 13 through it...after that I installed stock rom ....now when iam trying to install twrp recovery...it's showing no command....how to resolve it....
I searched about this issue in this forum but I didn't get the correct solution to solve the problem..
My device- Moto g3 xt1550
Android 6.0.1
Click to expand...
Click to collapse
Root with kingroot and flash twrp with flashify
I tried and successfully flashed twrp
Here is the link for kingroot https://king-root.net/d/kingroot_5_0_0.apk
no command
vamshi151 said:
unlocked bootloader and installed twrp recovery with that I installed cyanogenmod 13 through it...after that I installed stock rom ....now when iam trying to install twrp recovery...it's showing no command....how to resolve it....
I searched about this issue in this forum but I didn't get the correct solution to solve the problem..
My device- Moto g3 xt1550
Android 6.0.1
Click to expand...
Click to collapse
when u see no command just hold power then press volume up.........this will take u to stock recovery.......
jatintomar said:
Root with kingroot and flash twrp with flashify
I tried and successfully flashed twrp
Here is the link for kingroot https://king-root.net/d/kingroot_5_0_0.apk
Click to expand...
Click to collapse
NEVER USE KINGROOT OR KINGOROOT on a Moto G3 with Marshmallow, it will soft brick... We have seen at least a half dozen specific examples by experienced users... Somehow you got lucky, but I would never recommend this method to a user.
Now, once rooted Flashify is a viable option.
Hi,
as I did not find an English guide for rooting a BQ Aquaris M10 tablet and had some problems when trying to root my tablet, I want to post an guide how to root this tablet.
First of all:
- This guide is just from my experience and is not thoroughly tested. It's on your own if you risk bricking your device.
- If you get stuck in the process, in nearly all cases you can revert to stock with the MTK flash tool (can be found on mibqyyo.com) and the images provided by BQ on their website.
- I could not unlock the bootloader with the 1.X-Images (Lollipop), as the VolumeUp-Button didn't work in fastboot-mode and you need this button to confirm the unlock.
- Booting into recovery from start with VolumeUp and Power-Button. This doesn't work with the 1.X-images, too.
- This guide is not intended for users without experience in unlocking/rooting a device. If you don't know how to use adb, fastboot, recovery and things like that, don't try it!
- You will loose all your data during this process!!
Guide:
Modify boot.img, flash new firmware
SuperSU in systemless mode doesn't work on stock image, as the SuperSU installer can't extract boot.img. You have to repack boot.img.
I tried a SuperSU installer without systemless-mode, but device didn't even boot anymore afterwards.
This guide is derived from a Spanish tutorial on the HTCmania-forum ("Root M10 HD Marshmallow") by yquepongo. Thanks to him!
Get a firmware for your device from the BQ-website (should be Marshmallow, see above) and unzip it to a directory.
Extract the boot-verified.img in the firmware directory with a bootimg-extractor. There are various tools available.
I used bootimg.exe, because this was explained in the mentioned thread and I even used it with wine on Linux and it went well.
Search for cpiolist.txt in your extracted boot-verified.img and delete the first two lines:
mode:mtk
mtk_header_name:ROOTFS
Repack boot-verified.img and put it back in the firmware directory.
Flash the modified firmware with the MTK flash tool according to the tutorial on .mibqyyo.com (Title "Hard Reset for the smartphone range Aquaris and Aquaris E"). In short: Disconnect device, start Tool, load scatter file from firmware directory, choose firmware upgrade, start download, connect the device in power off state, download will start automatically.
This will delete all your data and put the device back to factory rom (hard reset)!!!
If you don't want to flash the complete firmware, you can flash only the boot-verified.img with "Download only" in the flash tool. I didn't try this and don't know if this is working.
Start your device, don't activate any security settings to prevent encryption of data partition.
Unlock bootloader, flash TWRP, install SuperSU
Enable developer settings on device and activate "OEM unlock" in developer settings.
Reboot into fastboot (adb reboot bootloader) and unlock bootloader (fastboot oem-unlock).
This will delete all your data!!! Reboot your system afterwards to make sure everything is still ok.
Do not activate any security settings and make sure your data partition is not encrypted!
The existing TWRP-image can't handle an encrypted data partition, you will end in a boot loop and have to start the whole process again!
Double check, your data partition isn't encrypted. (Settings - Security)
Reboot into fastboot (adb reboot bootloader) and flash the TWRP-image from the TWRP-site (fastboot flash recovery twrpxxx.img)
After reboot TWRP should start.
If you have checked that everything is ok (I would recommend a reboot into normal mode), you can install SuperSU with the standard-installer-zip in TWRP.
If you didn't modify your boot.img, the installer will give a warning that it cannot extract boot.img and you will not find any SuperSU on your system.
If you get stuck in bootloop afterwards you can start anew and try it with another image flashed with MTK flash tool. (Firmware 2.2.0 from December 2016 for freezerhd worked in my case)
Maybe some steps could be shortened, but I haven't tried it.
hi zrfl,
i have a bq aquarius m8 with mm os.
the m8 has the same resolution (1280x800)
can i try the twrp recovery from the m10?
i will also root my m8 but i cant extract the boot-sign.img.
all tools fails.
have you any ideas?
update:
yesterday i opened the bootloader. the volume button works in fastboot-mode.
also i can unlock the boot image with the tools from: https://forum.xda-developers.com/showthread.php?t=2073775
but the unpack fails:
Android Image Kitchen - UnpackImg Script
by osm0sis @ xda-developers
Supplied image: unlokied-new.img
Setting up work folders . . .
Splitting image to "/split_img/" . . .
Android boot magic not found.
Error!. . .
Click to expand...
Click to collapse
i think this bq boot image use non-standard header. any ideas how to root this bq aquarius m8?
i buyed this tablet only to can use xposed.
i think, any android without root or xposed is useless
i opened a separate theme for this : https://forum.xda-developers.com/android/general/root-help-to-root-twrp-recovery-bq-t3536170
dreas74 said:
hi zrfl,
i have a bq aquarius m8 with mm os.
the m8 has the same resolution (1280x800)
can i try the twrp recovery from the m10?
i will also root my m8 but i cant extract the boot-sign.img.
all tools fails.
have you any ideas?
update:
yesterday i opened the bootloader. the volume button works in fastboot-mode.
also i can unlock the boot image with the tools from: https://forum.xda-developers.com/showthread.php?t=2073775
but the unpack fails:
i think this bq boot image use non-standard header. any ideas how to root this bq aquarius m8?
i buyed this tablet only to can use xposed.
i think, any android without root or xposed is useless
Click to expand...
Click to collapse
Sorry, but I can't help you there, as the M8 seems to be too different to the M10: I didn't have to unlock the boot.img, it was easy to unpack.
hi zrfl,
thanks for your reply. i contacted the developer osmOsis from the android image kitchen.
he will implement the bq specials in his tools.
more in the AIK thread: https://forum.xda-developers.com/showthread.php?t=2073775&page=108
this is the only way to root this device !!
thanks a lot ...
Thanks for this tutorial.
I've followed all the step, I'm able to flash the new recovery from the TWRP website but then I do a
Code:
fastboot reboot-bootloader
but the device reboot normally, just with a warning message during boot saying something like "This device is unlock and can't be trusted, it will boot in 5 seconds".
So I'm unable to access TWRP recovery, I guess when the device reboot it override the recovery partition because if I do a
Code:
adb reboot recovery
I end up in the Android recovery not TWRP.
Any idea ?
Thanks
ZazOufUmI said:
Thanks for this tutorial.
I've followed all the step, I'm able to flash the new recovery from the TWRP website but then I do a
Code:
fastboot reboot-bootloader
but the device reboot normally, just with a warning message during boot saying something like "This device is unlock and can't be trusted, it will boot in 5 seconds".
So I'm unable to access TWRP recovery, I guess when the device reboot it override the recovery partition because if I do a
Code:
adb reboot recovery
I end up in the Android recovery not TWRP.
Any idea ?
Thanks
Click to expand...
Click to collapse
Sorry, I have done this a long time ago and don't know what could be wrong:
You have the correct message, so unlock was successfull
You try to reboot in fastboot, so you flashed TWRP correctly in fastboot-mode
And I don't have the device at hand to try it myself. But I do have a few suggestions, what you could try:
Don't try to shorten procedure with unlock and flashing of TWRP at once. I'm not sure, but I think I had problems when I tried this. So do a normal reboot after unlock, before booting again into fastboot and flashing TWRP. (Now you have done this already )
I don't remember the proper boot command after flashing of TWRP. But
Code:
fastboot reboot-bootloader
doesn't make sense: You are already in bootloader.
Is there a boot-option in the bootloader where you could choose recovery?
Otherwise better power off and use the key-combination for booting into recovery: VolumeUp+Power.
I think, you have to repeat the procedure, as recovery seems to be overwritten: Boot into fastboot, flash TWRP, reboot into recovery. And avoid normal booting before first boot into TWRP!
Did you use the newest TWRP 3.1.0 from March 8th? I haven't tried this yet, so there could be the problem. You could try the previous one: 3.0.2 from last year.
Thanks, I succeed with the combo key (power + vol up) directly after the reboot process
Perfect it's working great now !
I did exactly what you wrote but SuperSU won't install because it cannot extract the ramdisk...
Hi @zrfl
Thanks for your posting!
I did as you suggested and successfully unlocked bootloader and installed TWRP 3.1.1. Your hint to modify the boot-verified was extremely helpful, as I wouldn't be able to unlock the bootloader otherwise.
However, I did not manage to install super su. And boy, I tried many different versions od regular/system/systemless supersu, each flashed according to the respective how-to.
I ended up either in a bootloop, or get stuck on the Android logo at boot.
Flashing goes well until this step:
"Decompressing ramdisk
--- Failure, aborting"
I checked ramdisk compression of boot with Carliv image Kitchen and it tells me that it already is set to "gz" and not another compression TWRP can't handle.
Please help me on how to flash SuperSu.
Thanks and best
Tom
There is something wrong: TWRP does not need a modified boot.img.
Maybe newer ROM-versions are different.
Solution for geting root on BQ M10 FHD on stock rom 2.6.2: Start with a fresh system and install magisk beta (not stable), reboot and root is granted!
tanks a lot to @scafroglia93!
Are there any Custom ROM's
For this Tablet like CM/LineageOS AOSP etc?
Googling reveals nothing and Considering all the kernel mods like hardcore and Ubuntu touch I find it hard to believe that nobody has built one of the later.
I've been searching for custom ROMs too. Apparently, there are none available at present. However, I'd highly appreciate lineage rom.
Code:
Warning! any damage done to your device is not my fault, use at your own risk!
This zip should be used mainly if you wiped system for some reason and didn't back up, its TA-1060 May patch system image + kernel + vendor files
Unlocked bootloader required!
TWRP
1. Boot into TWRP
2. Format /data partition in TWRP
3. Use 'adb push ta_1060_oreo_may_18.zip /sdcard/' in windows/linux/mac
4. Go to sdcard in TWRP and flash ta_1060_oreo_may_18.zip
5. Reboot to bootloader
6. use 'fastboot flash recovery recovery.bin' (Link bellow)
7. Optional: fastboot oem lock
8. reboot
9. on boot you will get encryption, click on the reset button when android loads
10. You will reboot into recovery then back into system, done
Fastboot
1. Extract zip file
2. flash system.img, boot.img, vendor.img in fastboot
3. fastboot reboot
Links:
Stock ROM zip May
Recovery image
Good luck
XDA:DevDB Information
[ROM][STOCK][TWRP][27/06/18]TA-1060 Stock Oreo 8.1, ROM for the Nokia 1
Contributors
sooti
ROM OS Version: 8.x Oreo
Version Information
Status: Stable
Created 2018-06-27
Last Updated 2018-06-27
So we can flash either through TWRP or Fastboot right?
Zeenat11 said:
So we can flash either through TWRP or Fastboot right?
Click to expand...
Click to collapse
I haven't tested fastboot but it should work. TWRP works 100%
Thank you very much, you are a life saver!!
I was stuck in a TWRP loop.
I tried flashing through TWRP but it didn't work but the fastboot method worked like a charm!
My phone is running again.
Thank you very much.
Is there any userdata.img available?
alexstarc said:
Thank you very much.
Is there any userdata.img available?
Click to expand...
Click to collapse
Nope but do you really need it? just format in fastboot or TWRP.
sooti said:
Nope but do you really need it? just format in fastboot or TWRP.
Click to expand...
Click to collapse
For some reason on my unlocked nokia 1 it started to ask password after flash and boot and gkeyboard always crashes on boot. So, I thought flashing fresh userdata might help.
alexstarc said:
For some reason on my unlocked nokia 1 it started to ask password after flash and boot and gkeyboard always crashes on boot. So, I thought flashing fresh userdata might help.
Click to expand...
Click to collapse
I wrote in the instructions...
If you get a password just enter a random one, then it will ask you to wipe the device, click ok and it will reboot to recovery and then wipe userdata and boot fine.
just make sure you flash the recovery.bin and not twrp before you wipe
alexstarc said:
For some reason on my unlocked nokia 1 it started to ask password after flash and boot and gkeyboard always crashes on boot. So, I thought flashing fresh userdata might help.
Click to expand...
Click to collapse
Same happened to me. I solved it by a hard reset via the stock recovery.
Make sure you flash the recovery.bin like Sooti said.
Wiping through twrp doesn't work.
Nice, working twrp for Nokia 1.
I buyed this phone today. Waiting for customs
A little warning.
It looks like the recovery.bin I took from another nokia 1 device doesn't match the checksum check which causes a failed during ota updates, please only flash this rom if you soft bricked your device.
If anyone can get me TA-1060 stock recovery image that should solve it. for now you can't update the phone until a fix is found
I have Nokia Ta 1066. Will this rom work on mine? Also I read somewhere Ta 1060 is single sim variant. What about the second sim?
Has anyone with TA 1066 tried it?
Thanks. Both methods work fine. Don't ask how I found out.....
Can you share how you managed to backup stock recovery file. Maybe after all the steps above we can flash our own device recovery to make ota work again...
coolboyforeva said:
Can you share how you managed to backup stock recovery file. Maybe after all the steps above we can flash our own device recovery to make ota work again...
Click to expand...
Click to collapse
I don't have stock recovery from our device i have from another variant of Nokia 1
Hey guys i have a TA-1056 and after unlocking bootloader and flashing TWRP it booted to recovery and came up encrypted, after looking around the only solution was to format data, afterwards when rebooting it always boots to recovery, i tried flashing this zip and i get the same issue and i can't find the stock ROM for the 1056 anywhere online, can anyone help me out? i really appreciate it
Kurajmo said:
Nice, working twrp for Nokia 1.
I buyed this phone today. Waiting for customs
Click to expand...
Click to collapse
got any custom roms?
Does Nokia 1 support DT2W?
Sir, is that possible to get a stock rom of TA 1056 ?
I have searched everywhere but whole thing available over net just left my phone bricked. All i need is a working rom source. Even if that’s a custom rom too to flash via sp flash tool. Thanks in advance
Can any please repost the firmware , the link isn't working