Related
First, Happy Thanksgiving to any/all US users!
Happy Thursday to everyone else.
I have read the other threads related to bootloop issue, however, none seem to address my particular issue.
I will try to give as much info as I can......
I am rooted, unlocked bootloader, TWRP installed.
I used fastboot method, not a tool
I have Xposed, and have using several modules and have not experienced any issues until today.
I downloaded fonts from the playstore.
Made a nandroid backup.
I noticed when nandroid was running, it said something to the effect of no backup of boot and no backup of recovery.
I googled this and only found a few posts on the internet that mentioned it, and from what I could tell, I shouldn't worry about it ( :facepalm: )
Went into Xposed, placed a check next to ifonts, and rebooted phone.
I've been in a bootloop ever since.
I can boot into recovery, and attempted to restore the nandroid backup. When it completed, I restarted the system, only to find myself stuck in bootloop.
Went back into recovery, and did another restore from a backyup I did in TWRP a week ago.
When it completed and I restarted system....bootloop.......
OK!
So I thought perhaps I lost my boot image somehow.
Restarted to bootloader, and opened command prompt and ran
fastboot flash boot boot.img
Powered off the phone, then attempted to restart system.....bootloop.
Anyone have any suggestions/advice/directions?
I would be ever so grateful, and THANKFUL, for any assistance offered.
totallybeachin said:
First, Happy Thanksgiving to any/all US users!
Happy Thursday to everyone else.
I have read the other threads related to bootloop issue, however, none seem to address my particular issue.
I will try to give as much info as I can......
I am rooted, unlocked bootloader, TWRP installed.
I used fastboot method, not a tool
I have Xposed, and have using several modules and have not experienced any issues until today.
I downloaded fonts from the playstore.
Made a nandroid backup.
I noticed when nandroid was running, it said something to the effect of no backup of boot and no backup of recovery.
I googled this and only found a few posts on the internet that mentioned it, and from what I could tell, I shouldn't worry about it ( :facepalm: )
Went into Xposed, placed a check next to ifonts, and rebooted phone.
I've been in a bootloop ever since.
I can boot into recovery, and attempted to restore the nandroid backup. When it completed, I restarted the system, only to find myself stuck in bootloop.
Went back into recovery, and did another restore from a backyup I did in TWRP a week ago.
When it completed and I restarted system....bootloop.......
OK!
So I thought perhaps I lost my boot image somehow.
Restarted to bootloader, and opened command prompt and ran
fastboot flash boot boot.img
Powered off the phone, then attempted to restart system.....bootloop.
Anyone have any suggestions/advice/directions?
I would be ever so grateful, and THANKFUL, for any assistance offered.
Click to expand...
Click to collapse
your phone cant run without a boot.img, thats the kernel and it controls the whole phone. it would never ever boot up without. anyways, what you need to do is wipe data in twrp, then reflash your rom and supersu.
I don't want to sound ignorant, but I'm going to anyway...
Could you please tell me which file is my rom?
I followed the guide(s) for rooting, and downloaded the files as were instructed, and as far as I know, I didn't download a ROM.
Only a custom recovery (TWRP), a modified boot image, then flashed SuperSU through TWRP.
Is the ROM on my phone somewhere? I can boot into recovery and look through file manager.
I also have TitaniumBackup. Would it be in a backup from that app somewhere?
Oh I didn't see the above question. So no, while the rom is on your phone, it's not in any flashable form, so you should download the latest factory image for shamu and flash that, a modified boot image for that version, and then root it. Do a factory reset, clear cache and dalvik, and you shoulbe up and running.
factory reset/wipe data might fix it, if not, then you need to flash a factory image(since you dont have a flashable cystom rom).
In my files (with platform tools on my PC) I have a boot.img, recovery.img and a twrp.img......
is the recovery.img my rom?
I apologize if I come across as not getting it....flashing stock image will remove root, correct?
I would like to avoid this.
I will download a custom ROM if I have to, to avoid this, I just want to make sure I understand what I'm doing first.
If that recovery.img is not what I need, and stock WILL unroot, then I will gladly pull a custom rom.
Will I lose root if I do a factory reset?
totallybeachin said:
In my files (with platform tools on my PC) I have a boot.img, recovery.img and a twrp.img......
is the recovery.img my rom?
I apologize if I come across as not getting it....flashing stock image will remove root, correct?
I would like to avoid this.
I will download a custom ROM if I have to, to avoid this, I just want to make sure I understand what I'm doing first.
If that recovery.img is not what I need, and stock WILL unroot, then I will gladly pull a custom rom.
Will I lose root if I do a factory reset?
Click to expand...
Click to collapse
system.img is your rom. recovery.img is your stock recovery
---------- Post added at 02:34 PM ---------- Previous post was at 02:32 PM ----------
totallybeachin said:
In my files (with platform tools on my PC) I have a boot.img, recovery.img and a twrp.img......
is the recovery.img my rom?
I apologize if I come across as not getting it....flashing stock image will remove root, correct?
I would like to avoid this.
I will download a custom ROM if I have to, to avoid this, I just want to make sure I understand what I'm doing first.
If that recovery.img is not what I need, and stock WILL unroot, then I will gladly pull a custom rom.
Will I lose root if I do a factory reset?
Click to expand...
Click to collapse
factory reset and you wont lose root. factory.img and you will lose root. a custom rom requires twrp recovery, a custom kernel(for root), and the latest supersu.
Are you sure that it's not the xposed module is causing the bootloop??
use TWRP filemanager to delete /data/data/de.robv.android.xposed.installer/conf/modules.list
and try to boot again
Thanks for your assistance.......
I'm downloading Pure Nexus right now (and GApps), am I correct in my understanding that it already includes a kernal? I can change that if I want/need to, but it already has one, right?
eta:
Factory reset did nothing....
totallybeachin said:
Thanks for your assistance.......
I'm downloading Pure Nexus right now (and GApps), am I correct in my understanding that it already includes a kernal? I can change that if I want/need to, but it already has one, right?
Click to expand...
Click to collapse
Sure, otherwise it wouldn't boot
totallybeachin said:
Thanks for your assistance.......
I'm downloading Pure Nexus right now (and GApps), am I correct in my understanding that it already includes a kernal? I can change that if I want/need to, but it already has one, right?
eta:
Factory reset did nothing....
Click to expand...
Click to collapse
a rom always has a kernel included, as thats what ties the software rom to your hardware phone. it ties your cpu to it, your buttons, etc.. all to your rom. its also like the btain center to your phone.
Alright!
I seem to be back up and running.
Now I just have to spend the day getting my device back the way I had it before I crashed.
If I try and use my restore from Titanium Backup, will that mess anything up since it was made on a different ROM? Or, is that just a backup of my apps and stuff?
I want all my modules from Xposed, my wallpapers and stuff......
Thanks for all your help!
eta:
Also, SU says 'installed" in the play store, bu it's not showing up in my app drawer??? (And there is no option to 'uninstall' like any other app would have--weird)
totallybeachin said:
Alright!
I seem to be back up and running.
Now I just have to spend the day getting my device back the way I had it before I crashed.
If I try and use my restore from Titanium Backup, will that mess anything up since it was made on a different ROM? Or, is that just a backup of my apps and stuff?
I want all my modules from Xposed, my wallpapers and stuff......
Thanks for all your help!
eta:
Also, SU says 'installed" in the play store, bu it's not showing up in my app drawer??? (And there is no option to 'uninstall' like any other app would have--weird)
Click to expand...
Click to collapse
Maybe the dev has put an icon in settings for supersu.
And for future: don't forget the trick i posted above to disable modules
Droidphilev said:
Maybe the dev has put an icon in settings for supersu.
And for future: don't forget the trick i posted above to disable modules
Click to expand...
Click to collapse
Yeah...I found it there instead of app drawer.
And the 'trick'.....I didn't have this after data
de.robv.android.xposed.installer/conf/modules.list
Hello people,
I have an OnePlus 3T, which does not start the OS. I can open Fastboot Mode or TWRP. I do not even know which OS is installed (I think stock rom, but do not know). When I boot into Fastboot, I get the dm-verity notification "Phone is unlocked and cannot be trusted". When I boot into system, it stops at the black "Powered by android" Screen (very first screen).
When I connect my phone to the PC and open the internal storage, it shows only the "TWRP" folder.
So what Information do I have so far (with my amateur knowledge):
adb shell getprop ...
ro.build.version.release: 6.0.1
ro.build.version.sdk: 23
ro.build.display.id: omni_oneplus3-eng 6.0.1 MOB31K eng.jc.20170208.012427 test-keys
ro.modversion: OmniROM-6.0.1-20170208-oneplus3-HOMEMADE
ro.twrp.version: 3.0.4-1
When I start the bootloader:
Product_Name - msm8996
Variant - MTP UFS
Bootloader Version -
Baseband Version -
Serial Number - *****
Secure Boot - enabled
Device State - unlocked
I tried to reflash the original recovery => device did not start in recovery anymore => reflashed twrp
I tried to flash the stock ROM => did not work (with this Error 7)
So my first question: Which OS do I have? Really Marshmallow 6.0.1?
Second: Do you need more infos?
Third and most important: How to repair this mess?
What do I want: A stable, rooted ROM. It can be the stock ROM, but also a custom, I do not care right now.
I read that this unlocked-notification appears because I have the wrong kernel? Is that true? Which one do I need?
Thank you very much for your help.
Use ADB Sideload to Sideload a ROM onto the phone since you have TWRP working. It's not a huge problem, and it's easily solvable.
*OR* you can use the Unbrick tool to solve your problem.
thes3usa said:
Use ADB Sideload to Sideload a ROM onto the phone since you have TWRP working. It's not a huge problem, and it's easily solvable.
*OR* you can use the Unbrick tool to solve your problem.
Click to expand...
Click to collapse
Thank you for your reply.
Okay so it is not important which system I run right now? And what about this kernel thing?
I can just flash it with sideload (e.g. https://forum.xda-developers.com/on...pment/rom-kernel-resurrectionremix-n-t3524715) and finished? Rooted and particularly working?
Sorry for the questions but I am a little nervous
elchico92 said:
Thank you for your reply.
Okay so it is not important which system I run right now? And what about this kernel thing?
I can just flash it with sideload (e.g. https://forum.xda-developers.com/on...pment/rom-kernel-resurrectionremix-n-t3524715) and finished? Rooted and particularly working?
Sorry for the questions but I am a little nervous
Click to expand...
Click to collapse
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
thes3usa said:
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
Click to expand...
Click to collapse
So first this one (downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_21/), then this (androidfilehost.com/?w=files&flid=131965 - latest)?
Thanks again!
PS: Sorry I cannot post links yet.
elchico92 said:
So first this one (downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_21/), then this (androidfilehost.com/?w=files&flid=131965 - latest)?
Thanks again!
PS: Sorry I cannot post links yet.
Click to expand...
Click to collapse
Nope, that's the complete stock Zip. Unless you want to install OOS, that's not the one to Sideload.
Download the FW only from here: https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166
And then Sideload it, reboot back to recovery, and then Sideload the ROM.
elchico92 said:
When I connect my phone to the PC and open the internal storage, it shows only the "TWRP" folder.
Click to expand...
Click to collapse
What is in the TWRP folder, anything? The TWRP folder would normally only be created, if a backup was created. You can possibly just boot TWRP, select the RESTORE option, select the backup from the TWRP folder, and get the phone up and running again.
Another possibility, if you aren't that up on adb commands (sideload, etc.), since you can access the internal storage, just download a ROM or fill stock ROM zip onto your PC, then just drag/copy to internal storage. Then boot TWRP, select INSTALL, pick the file, and flash it.
What is the background of the device, how do you not know the OS version? Did you receive it this way, or fixing it for a friend or something?
---------- Post added at 09:19 AM ---------- Previous post was at 09:12 AM ----------
elchico92 said:
When I boot into Fastboot, I get the dm-verity notification "Phone is unlocked and cannot be trusted".
I read that this unlocked-notification appears because I have the wrong kernel? Is that true? Which one do I need?
Click to expand...
Click to collapse
That isn't the dm-verity notification. The dm-verity notification screen is similar, but says "dm-verity is not started in enforcing mode".
What you described is the bootloader unlocked warning screen. The bootloader unlocked warning screen is expected and normal (in fact, unavoidable) if the bootloader is unlocked. And unlocked bootloader is required for TWRP, flashing custom ROMs, etc.
dm-verity warning screen is in fact normal, as well, if you have TWRP installed. That one can be disabled by a couple different methods. But it's only purpose is to notify a "average" user that the system has been modified. For XDA users that are intentionally modifying their phones (TWRP, root, etc.) the warning is pretty meaningless. Under certain conditions, dm-verity will prevent the phone from booting. But TWRP and root in themselves, will normally not do that.
Neither warning means you have the wrong kernel, necessarily. And unless you (or someone else) tried to flash a kernel, there really isn't any reason to believe that.
---------- Post added at 09:29 AM ---------- Previous post was at 09:19 AM ----------
elchico92 said:
I tried to reflash the original recovery => device did not start in recovery anymore => reflashed twrp
Click to expand...
Click to collapse
Flashing stock recovery will (by definition) replace TWRP with stock recovery. You probably have recovery, just the stock one (not TWRP) which is fairly useless in your case (can't flash custom ROMs, root, etc.).
elchico92 said:
I tried to flash the stock ROM => did not work (with this Error 7)
Click to expand...
Click to collapse
Can't really troubleshoot this, unless you tell us what file exactly (file name) and where you got it from. "Stock ROM" is far too vague, and can literally mean a dozen or more different things.
Also, what version TWRP?
Using a TWRP version which does not support Oreo is one reason for Error 7. Or you may have tried a file intended for the 3, not the 3T. So these details need to be provided, before we can figure out what went wrong.
elchico92 said:
What do I want: A stable, rooted ROM. It can be the stock ROM, but also a custom, I do not care right now.
Click to expand...
Click to collapse
You kind of need to decide which of those you want. Otherwise, there are just too many options for us to give.
Yet another option (in addition to those given) would be to flash the full stock OOS zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Then before rebooting, flash Magisk to root, and you should be all set. The full zip will put you on a fully stock baseline (including firmware). Which, if you aren't sure if you want stock, beta or custom ROM, is not a bad place to be; you can see what the "stock" condition is, before messing with things like custom ROMs. But again, it's totally subjective and a matter of personal preference, and you really do need to decide for yourself what is best for you (as an individual) at this time.
thes3usa said:
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
Click to expand...
Click to collapse
Why not just sideload stock ROM which includes the firmware? Make life easier
przemcio510 said:
Why not just sideload stock ROM which includes the firmware? Make life easier
Click to expand...
Click to collapse
Yeah, that is a good option, among many. As I mentioned, there are just too many options since the original poster hasn't even decided stock or custom ROM.
przemcio510 said:
Why not just sideload stock ROM which includes the firmware? Make life easier
Click to expand...
Click to collapse
Since OP hasn't mentioned whether he wants to use a stock or custom ROM. So I gave him the link for the latest FW, in case he wants to use a recently updated custom ROM without needing to download the whole Stock zip.
Done!
Thanks a lot. The phone is working again.
I have flashed with adb sideload the firmware and the ResurrectionRemix-Rom (Nougat) and then via TWRP the gapps.
So I hope, everthing will be fine now.
answers:
- TWRP-folder: yeah I created one because I thought, maybe to restore will fix anything
- I tried to flash with TWRP a ROM, but it says "Error 7", which means: wrong ROM => but I am sure, it was the right one
- background: it was the phone of a friend of mine => he never heard anything about ROMs etc
The thread can be closed.
elchico92 said:
- I tried to flash with TWRP a ROM, but it says "Error 7", which means: wrong ROM => but I am sure, it was the right one
Click to expand...
Click to collapse
I already offered to troubleshoot this error for your, but you never supplied the requested info. Don't assume it is the "right one" next time, but rather, give exact file names, version numbers, and let us verify. Mistakes happen, and it always is good to have another set of eyes look at the specifics.
---------- Post added at 09:58 AM ---------- Previous post was at 09:56 AM ----------
elchico92 said:
The thread can be closed.
Click to expand...
Click to collapse
Threads on xda don't get closed, just because you solved your current issue. Others may have a similar problem, and may want to ask questions, etc.
I'm stuck in Fastboot Mode & TWRP without OS
I everyone,
Like the title say I'm totally stuck, I don't know what to do ....
I've got a OnePlus 3T few years ago, and the first thing i did at the installation was to encrypt the phone with an option of oxygen OS, and after that i unlock the oem and add root access.
But when oneplus release a major update, there was issues with phone encrypted and unlock, for that I never could make an update of the OS, so I did try to install the lastest lineage os recently, and add an "error 7".
After reading a lot of stuff and try a lot of manupilations, i'm now totally stuck with only access to the fastboot, twrp, and the recovery of oneplus.
If someone here could help me, you will be very gratefull because i can't afford to buy a new phone for the moment... thank's
slykereven said:
I everyone,
Like the title say I'm totally stuck, I don't know what to do ....
I've got a OnePlus 3T few years ago, and the first thing i did at the installation was to encrypt the phone with an option of oxygen OS, and after that i unlock the oem and add root access.
But when oneplus release a major update, there was issues with phone encrypted and unlock, for that I never could make an update of the OS, so I did try to install the lastest lineage os recently, and add an "error 7".
After reading a lot of stuff and try a lot of manupilations, i'm now totally stuck with only access to the fastboot, twrp, and the recovery of oneplus.
If someone here could help me, you will be very gratefull because i can't afford to buy a new phone for the moment... thank's
Click to expand...
Click to collapse
This should get you back to OOS:
In TWRP:
1. Do a factory reset
2. Flash OOS 9.0.6 full rom
3. Flash this modified firmware (to avoid the issue 9.0.6 with encrypted+unlocked) https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip (see https://forum.xda-developers.com/on...5-0-8-firmware-barrier-t3941164/post79758055)
4. Reboot
This should leave you with a clean install of OOS 9.0.6 and an encrypted phone with the stock recovery (TWRP gets replaced when you boot stock OOS).
From that point you can do what you want.
Sent from my OnePlus 3T using XDA Labs
Resolved
OK, that's a little crazy but it's working, i've got a one plus 3T A3003, but i had to install Stable9.0.3+Firmware+Modem_OnePlus3.zip and not the one for the 3T ..... then install the last lineage os 17, and everything seems to work for now !!!
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
BillGoss said:
This should get you back to OOS:
In TWRP:
1. Do a factory reset
2. Flash OOS 9.0.6 full rom
3. Flash this modified firmware (to avoid the issue 9.0.6 with encrypted+unlocked) https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip (see https://forum.xda-developers.com/on...5-0-8-firmware-barrier-t3941164/post79758055)
4. Reboot
This should leave you with a clean install of OOS 9.0.6 and an encrypted phone with the stock recovery (TWRP gets replaced when you boot stock OOS).
From that point you can do what you want.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Hi, thank's for your help, i didn't see your answer before and i have resolved the issue with other method
houston we have a problem...
5 bucks for any good idea!
I have an old xt1068 (titan) that after an (official) update it becames a small brick... (it was stock, no modded bootloader or whatevere, just stock!)
today I decided to give it a chance but then only thing I reach is the bootloader
whatever thing (official retail firmware) I try to flash it doesn't work...
so I unlocked the bootloader with success to give a try a custom rom but suddenly I get a issue...
I can't install latest twrp (I tried also a couple of older ones), I can only boot trough (latest) twrp but whatever rom I install I get error7
I noticed that when it reboots the content (/sdcard /data and /system) is untouched even if from shell I can remount rw... it seems that I can delete but in reality I don't delete anything
I tried almost everything... if I try to re-stock upon reboot I reach the dead android robot
the device is an xt1068, bootloader 48.87 (30.06.2016), unlocked (status code 3)
any (good) ideas?
O this thing is happened to me , i has on stock 5.0 and i updated to a new version ,but after i get only bootloop so i unlocked the bootloader and flash the latest twrp , and if i try to install any custom rom twrp give me some partition are corrupt. Enter in TWRP open WIPE > Advanced Wipe > (check your corrupt partition ,in my case is the data) > Repair or Change File System > Change File System > Ext3 or Ext4 > Swipe to Change (if this don't work try olso resize partition or repair partition)
HiR3x said:
O this thing is happened to me , i has on stock 5.0 and i updated to a new version ,but after i get only bootloop so i unlocked the bootloader and flash the latest twrp , and if i try to install any custom rom twrp give me some partition are corrupt. Enter in TWRP open WIPE > Advanced Wipe > (check your corrupt partition ,in my case is the data) > Repair or Change File System > Change File System > Ext3 or Ext4 > Swipe to Change (if this don't work try olso resize partition or repair partition)
Click to expand...
Click to collapse
no way... I tried but nothing changes... it seems that partitions are read-only
anyway I'm not able to flash twrp (no error it just doesn't install), I can only boot twrp but again nothing changes, I tried soon after booting twrp to gain root trought supersu/magisk, all works without error but upon reboot partitions aren't touched at all
I have the exact same issue on the exact same phone.
However, what I have noticed is the fact that after SuperSu is flashed (Booting through TWRP recovery once), it doesn't actually flash at all. But what surprised me was that after the flashing, the phone reboots instead of taking me back to the recovery.
A good idea would be that maybe the bootloader isn't actually unlocked for everything. Maybe the company making the device just doesn't want us to get a new one.
In any case, I never give. I will keep trying.
---------- Post added at 09:08 AM ---------- Previous post was at 08:37 AM ----------
The solution is simply using a different TWRP version. I had mentioned my concerned earlier and I was right. We wer einitially flashing a wrong TWRP in the device and hence the problem. I found the solution in this video here: https://www.youtube.com/watch?v=9_9vkJvzWcU
However, the TWRP and Su can be found here if the guy who uploaded the video has deleted it:
https://drive.google.com/open?id=1rSyDJoeOVVFHCbNa_jkfH9HUnDoZqBhd
I am glad to hear that it helped you to resolve your problem
ni6hant said:
I have the exact same issue on the exact same phone.
However, what I have noticed is the fact that after SuperSu is flashed (Booting through TWRP recovery once), it doesn't actually flash at all. But what surprised me was that after the flashing, the phone reboots instead of taking me back to the recovery.
A good idea would be that maybe the bootloader isn't actually unlocked for everything. Maybe the company making the device just doesn't want us to get a new one.
In any case, I never give. I will keep trying.
---------- Post added at 09:08 AM ---------- Previous post was at 08:37 AM ----------
The solution is simply using a different TWRP version. I had mentioned my concerned earlier and I was right. We wer einitially flashing a wrong TWRP in the device and hence the problem. I found the solution in this video here: https://www.youtube.com/watch?v=9_9vkJvzWcU
However, the TWRP and Su can be found here if the guy who uploaded the video has deleted it:
https://drive.google.com/open?id=1rSyDJoeOVVFHCbNa_jkfH9HUnDoZqBhd
Click to expand...
Click to collapse
I am glad to hear that it helped you to resolve your problem all the required downloading links are working fit and fine it's my channel show me some love via comments and likes on my video
mandar91 said:
I am glad to hear that it helped you to resolve your problem all the required downloading links are working fit and fine it's my channel show me some love via comments and likes on my video
Click to expand...
Click to collapse
Already commented a liked.
ni6hant said:
I have the exact same issue on the exact same phone.
However, what I have noticed is the fact that after SuperSu is flashed (Booting through TWRP recovery once), it doesn't actually flash at all. But what surprised me was that after the flashing, the phone reboots instead of taking me back to the recovery.
A good idea would be that maybe the bootloader isn't actually unlocked for everything. Maybe the company making the device just doesn't want us to get a new one.
In any case, I never give. I will keep trying.
---------- Post added at 09:08 AM ---------- Previous post was at 08:37 AM ----------
The solution is simply using a different TWRP version. I had mentioned my concerned earlier and I was right. We wer einitially flashing a wrong TWRP in the device and hence the problem. I found the solution in this video here: https://www.youtube.com/watch?v=9_9vkJvzWcU
However, the TWRP and Su can be found here if the guy who uploaded the video has deleted it:
https://drive.google.com/open?id=1rSyDJoeOVVFHCbNa_jkfH9HUnDoZqBhd
Click to expand...
Click to collapse
thank you for help but it didn't work... rebooting into recovery lands me on "dead robot" saying "no command", then after 1 minute it reboots... and reboots... and so on...
I think I tried almost everything... I'm really lost
How come!
How can it happen. It is Moto G 2?
suiller said:
thank you for help but it didn't work... rebooting into recovery lands me on "dead robot" saying "no command", then after 1 minute it reboots... and reboots... and so on...
I think I tried almost everything... I'm really lost
Click to expand...
Click to collapse
ni6hant said:
How can it happen. It is Moto G 2?
Click to expand...
Click to collapse
this is what I see from bootloader...
so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help
Um, i think ur in the wrong category
thejacer87 said:
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps ...
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is?
Click to expand...
Click to collapse
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)
Fatal_Scythe said:
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)
Click to expand...
Click to collapse
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions
thejacer87 said:
so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help
Click to expand...
Click to collapse
If you're planning to go back to stock MIUI and locked bootloader, I highly recommend using Mi Flash and flashing the original fastboot MIUI ROM which can be found here https://www.xda-developers.com/download-miui-11-xiaomi-redmi-note-7-pro-poco-f1/amp/. All you gotta to do is extract the ROM file which is .tgz to any folder, and in Mi Flash select that folder click on "clean all and lock" in the bottom right corner, and click flash. This should theoretically make your device "out of the box".
Keep in mind that this method requires a PC with all ADB and fastboot drivers, they can be downloaded from here https://forum.xda-developers.com/showthread.php?t=2588979 .
thejacer87 said:
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions
Click to expand...
Click to collapse
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too
Fatal_Scythe said:
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too
Click to expand...
Click to collapse
just got gpay to work with the sql fix. thanks for the help
After the Jan update to crdroid 9 I have been completely unable to load twrp back onto my phone. I have never had any problems with this before, but now after trying for the third time I am stuck in my third bootloop. I have tried 'install current twrp' 'install to ramdisk' and used two different versions of twrp the result is always the same, stuck in fastboot. So first question - is there a way to get out of the bootloop without having to do a third factory reset because they are doing my head in? Second question - is there a way to get twrp installed any more on this rom? I tried changing slots but it makes no difference. Because it is stuck in fastboot I can 'fastboot boot twrp' to do any flashing/wiping that may be necessary, but so far I have only been able to get the phone back with a factory reset. Any help appreciated.
viking777 said:
After the Jan update to crdroid 9 I have been completely unable to load twrp back onto my phone. I have never had any problems with this before, but now after trying for the third time I am stuck in my third bootloop. I have tried 'install current twrp' 'install to ramdisk' and used two different versions of twrp the result is always the same, stuck in fastboot. So first question - is there a way to get out of the bootloop without having to do a third factory reset because they are doing my head in? Second question - is there a way to get twrp installed any more on this rom? I tried changing slots but it makes no difference. Because it is stuck in fastboot I can 'fastboot boot twrp' to do any flashing/wiping that may be necessary, but so far I have only been able to get the phone back with a factory reset. Any help appreciated.
Click to expand...
Click to collapse
I should first try to reflash the firmware for your device. That's something to try first.
Just flash other ROM and wipe data. If doesn't help, flash firmware for your device like @minionguy said.
Update - I got back to a working system without a factory reset by fastbooting twrp going to restore and restoring the boot partition only from my latest twrp backup, so that answers Q1. As for Q2 (how to get twrp installed I still don't know how to do that).
Thanks for the replies btw. I think if that is the only way to install twrp I will have to live without it for now. I know I am not the only one with this problem there have been other reports elsewhere. Somebody suggested sideloading, but I can't find a zip file for the twrp version I am using ( twrp-3.7.0_12-0-spes-A12-dblenk9) and this is the only version I have found that works properly since it successfully decrypts data whereas the other versions I have used don't even bother to try, making them useless.
viking777 said:
Update - I got back to a working system without a factory reset by fastbooting twrp going to restore and restoring the boot partition only from my latest twrp backup, so that answers Q1. As for Q2 (how to get twrp installed I still don't know how to do that).
Thanks for the replies btw. I think if that is the only way to install twrp I will have to live without it for now. I know I am not the only one with this problem there have been other reports elsewhere. Somebody suggested sideloading, but I can't find a zip file for the twrp version I am using ( twrp-3.7.0_12-0-spes-A12-dblenk9) and this is the only version I have found that works properly since it successfully decrypts data whereas the other versions I have used don't even bother to try, making them useless.
Click to expand...
Click to collapse
This is where I borked it myself, and with sideloading. Apparently, the semi-permanent instructions for TWRP on spes should work using twrp-3.7.0.img (96mb) and NOT twrp-3.7.0-12.1-06.11.22.img (128mb), as the latter is the JabiYeff version and is "unable to flash MIUI ROMs due to dynamic partitioning error" as of November 2022. I assume your dblenk9 version is 128mb? You have a link for it? Googling gives only this thread and a couple of Russian sites 4pda.to. I just stayed on the stock crDroid recovery; did the same on my RN10P after this same ROM.
Flash crd9.1 on spes using instructions by LolFlasherNoob with the full MIUI ROM flashed first.
Sheist! said:
This is where I borked it myself, and with sideloading. Apparently, the semi-permanent instructions for TWRP on spes should work using twrp-3.7.0.img (96mb) and NOT twrp-3.7.0-12.1-06.11.22.img (128mb), as the latter is the JabiYeff version and is "unable to flash MIUI ROMs due to dynamic partitioning error" as of November 2022. I assume your dblenk9 version is 128mb? You have a link for it? Googling gives only this thread and a couple of Russian sites 4pda.to. I just stayed on the stock crDroid recovery; did the same on my RN10P after this same ROM.
Flash crd9.1 on spes using instructions by LolFlasherNoob with the full MIUI ROM flashed first.
Click to expand...
Click to collapse
@Sheist!
Thanks for the reply.
Re the dblenk9 twrp, it definitely came from this site somewhere but I can't find the link any more either, nor on the wider internet. The version I use is 96mb and it has worked very well up until the Jan update. Like yourself, I will stay on crdroid recovery for now, but I will attach the dblenk9 twrp version to this post in case you or anyone else is interested. You can still use it for 'fastboot boot twrp' and it does decrypt data so you are not left with 0mb on internal storage like the others I have tried.
NB To anyone who happens across this post whilst looking for twrp versions, If you are on the Jan ota do not try to install this, only fastboot it - unless you enjoy bootloops!
It probably doesn't matter much now, but I managed to find the original post that linked to the dblenk9 twrp this is it:
Any one have OrangeFox Recovery for Redmi Note 11 (spes)?
I am looking for OrangeFox Recovery for RN 11 (spes). Couldn't find anywhere. Anybody build it?
forum.xda-developers.com
It shows how good the search is on this forum because I wasn't even looking for it!