Related
Firstly, thanks to SafinWasi and Red_81 who both helped me on other threads, this question follows on from those threads.
I'm trying to downgrade from 7.4.9 user 4952320. Eventually, I will probably install CM11 (I tried once and bricked my device), but for now I just want to downgrade the OS and be able to change the wallpaper, I'm sick of the black paper. (I've tried Stunts wallpaper fix and it didn't work)
When the device upgraded to 7.4.9 I made backups of the whole 12 img files (inc boot0block).
I've read that you need a 7.2.3 boot image to be able to install TWRP as part of the CM11. I obtained a rooted 7.2.3 boot image from Red_81s google drive. I then flashed that boot image and tried rebooting the device. No joy. I got the red triangle. I flashed my 7.4.9 boot image and rebooted. The device rebooted and worked as normal.
I then flashed the 7.2.3 rooted system image and rebooted. Again I got the red triangle. I then flashed the 7.2.3 boot image, (so the device had 7.2.3 system and boot images) but again I got the red triangle.
So, how do you downgrade? Should I have flashed all 3 of the 7.2.3 images? (I don't have the checksums of the images so I recognise if one of the images was corrupted the exercise was doomed to failure.)
By flashing my 7.4.9 system and boot images, my device was restored to functionality, and I learned a bit, but not enough to achieve the goal. I'm hoping someone can show me how to downgrade.
Thought I'd add that I did try Kindle Fire First Aide but got lots of errors about dropbox not being available.
Did you flash the system and recovery? Both are needed to successfully downgrade. I always wipe data too.
Sent from my Nexus 7 using XDA Premium 4 mobile app
cecr said:
.
Click to expand...
Click to collapse
You need to flash a custom recovery on a second bootloader as well. You can't just flash the system. You also need to flash the 7.2.3 boot.img and stack override. Any tutorial dealing with this mod will include all the steps. It important to pay attention to details and not skip any steps. http://forum.xda-developers.com/showthread.php?t=2128848
Sent from my Nexus 7 Flo running Paranoid Android 4.4.3 using XDA premium 4 mobile app
Red_81 said:
Did you flash the system and recovery? Both are needed to successfully downgrade. I always wipe data too.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I didn't flash recovery, at my first attempt, just boot, then I tried boot & system. Both tries gave the red triangle.
I've tried again, with all 3 rooted images from your gdrive - recovery, boot & system, and again got the red triangle. I tried again with the 3 images from another source (my own unrooted 7.2.3 backup when I first got the HD7) and again, got the red triangle.
I haven't wiped the data because I would prefer to keep it so I can use the device (and think it should be possible to downgrade without wiping). I haven't been able to find a command to wipe just the cache...
So I'm more than a bit puzzled. The fastboot commands (eg fastboot -i 0x1949 flash boot boot.img) all return with "sending" then "OKAY", then "writing", then "OKAY" so I don't think there's any problem there.
I must be doing something wrong or missing something.
LinearEquation said:
You need to flash a custom recovery on a second bootloader as well. You can't just flash the system. You also need to flash the 7.2.3 boot.img and stack override. Any tutorial dealing with this mod will include all the steps. It important to pay attention to details and not skip any steps. http://forum.xda-developers.com/showthread.php?t=2128848
Sent from my Nexus 7 Flo running Paranoid Android 4.4.3 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your response, but at this stage I don't want to flash a new custom ROM, that may (probably will) come later, but at this stage I want to just downgrade. I've been warned that installing TWRP etc may leave the stock system in a bootloop, so a working stock backup won't be possible.
As I have to downgrade the stock boot image anyway in order to install a custom ROM, I thought I'd downgrade the whole OS in order to have a functioning stock system, then I can make a backup of it in TWRP, then install a custom ROM.
If I'm having problems with a simple downgrade, I might have more severe problems flashing a new ROM and be left with a dead device like I was previously, hence my caution and not wanting to move on until I know I can recover to the previous step if things go wrong.
Did you try downloading the original 7.2.3 from the thread and try flashing them ?
Red_81 said:
Did you try downloading the original 7.2.3 from the thread and try flashing them ?
Click to expand...
Click to collapse
Yes, I did. Tried them twice, in a different order (didn't think it would make a difference but you never know....). Anyway, tried again, this time, wiped data and cache (took 45 mins) and it worked! I now have 7.2.3 and access to Gplay (was already there).
I haven't registered it to my Amazon account yet, so email and contacts don't work, and am wondering if I should go straight to installing a custom ROM. I'm thinking if it isn't registered to Amazon, then they can't update it via OTA...... or can they?
It's been a bit of a task getting this far, but at least I'm more confident about getting into ADB and Fastboot!
cecr said:
I'm thinking if it isn't registered to Amazon, then they can't update it via OTA...... or can they?
Click to expand...
Click to collapse
well, I know the answer, yes, even though it hasn't logged into an Amazon account (I realise they pre-register them to your account before dispatch), it updated back to 7.4.9 just as I finished the above post and whilst I was thinking I should disable OTA updates using KFFA!
flip. This is turning into hard work. lol, still I know how to do it now.
I was having many issues after the last OTA and got mine to cm-11-20140609-SNAPSHOT-M7 last night. Mine was at 7.4.9 also. I followed rootjunky youtube videos to get mine re-rooted, flashed and working. After getting it rooted, he uses Fire Flash app to put twrp on the Kindle. I deviated a little and put the twrp 2.7.0.0 version other than that, I followed to a T. Once I got all that done, I went on the internet to Hashcode's repository and downloaded the newest cm-11 UNOFFICIAL he had listed directly to the device. I downloaded the latest Gapps from cyanogenmod and then booted into recovery(twrp) and installed. Everything is working beautifully now. Everything seems faster and smoother so far. I did go ahead and do an update from the about area in the settings to cm-11-20140609-SNAPSHOT-M7. I was also able to get all my books that I had purchased through kindle in the kindle reader.
greg2074 said:
I was having many issues after the last OTA and got mine to cm-11-20140609-SNAPSHOT-M7 last night. Mine was at 7.4.9 also. I followed rootjunky youtube videos to get mine re-rooted, flashed and working. After getting it rooted, he uses Fire Flash app to put twrp on the Kindle. I deviated a little and put the twrp 2.7.0.0 version other than that, I followed to a T. Once I got all that done, I went on the internet to Hashcode's repository and downloaded the newest cm-11 UNOFFICIAL he had listed directly to the device. I downloaded the latest Gapps from cyanogenmod and then booted into recovery(twrp) and installed. Everything is working beautifully now. Everything seems faster and smoother so far. I did go ahead and do an update from the about area in the settings to cm-11-20140609-SNAPSHOT-M7. I was also able to get all my books that I had purchased through kindle in the kindle reader.
Click to expand...
Click to collapse
Nice to know. Think I'll be doing something very similar, now I've made backups of 7.4.9 "just in case". Just have to go through all the above again!
I intend to create a post with how to do things on this phone.
Just bought the 64GB Black.
So, trying to pull the order of things to be done.
Please help, this is for newbies.
When you receive it. What should be done first? (and how did you do it???)
(EDIT : I will update this as I find things out.)
Bootloader
Follow the guide found here : http://xiaomitips.com/guide/unlock-mi-5-bootloader/
You should do this in advance of getting your phone.
Recovery - TWRP
Guide here : http://en.miui.com/thread-245756-1-1.html
Which ROM to install?
CM alternative?
Gapps?
If you own the Mi5, how did you go about it? Any tips? What went wrong? How did you fix?
First I unlocked my bootloader, which is essential to do first. Then I flashed TWRP using the ADB terminal thing on my computer via USB. After I had TWRP, I rooted my phone using SuperSU. But I was bored of MIUI so I flashed Cyanogenmod 13 in the thread in the MI 5 ROM forum. I have not changed anything since then really, I'm using the root that comes with CM now. It's all really good.
Edit: make sure you flash google apps at the SAME TIME as cyanogenmod! Without booting in between! Also the snapchat camera doesn't work right now for CM but if you use the app casper.io (not on play store, google it) you can use the phones camera app and then it works fine.
regnarox said:
First I unlocked my bootloader, which is essential to do first. Then I flashed TWRP using the ADB terminal thing on my computer via USB. After I had TWRP, I rooted my phone using SuperSU. But I was bored of MIUI so I flashed Cyanogenmod 13 in the thread in the MI 5 ROM forum. I have not changed anything since then really, I'm using the root that comes with CM now. It's all really good.
Edit: make sure you flash google apps at the SAME TIME as cyanogenmod! Without booting in between! Also the snapchat camera doesn't work right now for CM but if you use the app casper.io (not on play store, google it) you can use the phones camera app and then it works fine.
Click to expand...
Click to collapse
Which TWRP did you use (link?)
Which GApps did you use? (Nano, pico, stock etc) and presumably ARM64?
since there isn't a sdcard, are you able to do a full backup so you can revert back to if you have second thoughts. I guess you have to do a full wipe prior to flashing e.g CM13
Questions about rooting
Hey I got a Mi5 64GB with unlocked bt and twrp installed.
Now I want to root the device but when I boot to twrp I can't flash files because the device is encrypted by default and in order to decrypt it I need to perform a full wipe or enter a password, I don't know the password because it's not a password I decided on, I don't really have a problem doing a full wipe I don't have any important data.
But here are my questions:
1. If I'll do a full wipe will I have to install MiUi and twrp again?
2. Right now if I connect my phone to my PC using USB when it's in recovery mode I can't use MTP and if I'll perform a full wipe the SuperSU.zip will get deleted from my device and I will have to get it back to the device somehow and I can't because I can't use MTP when I'm in recovery mode. So I thought maybe after the full wipe I will be able to use MTP on recovery maybe I can't because it's encrypted at the moment?
Thanks
TWRP - https://www.androidfilehost.com/?fid=24533103863138514 (no touch screen issue which is present in other recoveries)
GApps - http://opengapps.org/ (ARM64) I used microG instead of gapps to save a lot of battery. (You can google it if you want)
It doesn't really matter what GApps do you use, although I'd go for nano/pico. I wouldn't want all the GApps to be my system apps.
---------- Post added at 11:11 AM ---------- Previous post was at 11:02 AM ----------
Sachuan said:
Hey I got a Mi5 64GB with unlocked bt and twrp installed.
Now I want to root the device but when I boot to twrp I can't flash files because the device is encrypted by default and in order to decrypt it I need to perform a full wipe or enter a password, I don't know the password because it's not a password I decided on, I don't really have a problem doing a full wipe I don't have any important data.
But here are my questions:
1. If I'll do a full wipe will I have to install MiUi and twrp again?
2. Right now if I connect my phone to my PC using USB when it's in recovery mode I can't use MTP and if I'll perform a full wipe the SuperSU.zip will get deleted from my device and I will have to get it back to the device somehow and I can't because I can't use MTP when I'm in recovery mode. So I thought maybe after the full wipe I will be able to use MTP on recovery maybe I can't because it's encrypted at the moment?
Thanks
Click to expand...
Click to collapse
1. You just need to format data, your system partition will not be wiped. You will just lose everything except the system.
2. You probably will be able to use MTP, although I'm not but other people are so you should too. If you don't, you'll need to go to advanced in TWRP, enter adb sideload and sideload the zip.
[I deleted your quote becasue it said I can't post outside links]
Ok, thank you!
(I don't need to install twrp again right?)
Sachuan said:
[I deleted your quote becasue it said I can't post outside links]
Ok, thank you!
(I don't need to install twrp again right?)
Click to expand...
Click to collapse
No, you don't
proag said:
No, you don't
Click to expand...
Click to collapse
Good thanks!
Sent from my MI 5 using XDA-Developers mobile app
Ive downgraded to 5.1.2 and I found out that you need to run KingRoot a few times to get root, after that how do I get TWRP and then Cyanogenmod? Ive looked everywhere today and a lot of the tutorials are outdated or dont work.
Edit: OK ive rooted now and have Super SU installed, how do I get TWRP? (So I can flash Cyanogenmod and backup)
Im in fastboot and the command "fastboot boot TWRP_Fire_recovery.img" I replaced the "TWRP_Fire_recovery.img" with the TWRP disk image and its failing but I am connected and the device is being recognized. HELP?
MMS21 said:
Ive downgraded to 5.1.2 and I found out that you need to run KingRoot a few times to get root, after that how do I get TWRP and then Cyanogenmod? Ive looked everywhere today and a lot of the tutorials are outdated or dont work.
Edit: OK ive rooted now and have Super SU installed, how do I get TWRP? (So I can flash Cyanogenmod and backup)
Im in fastboot and the command "fastboot boot TWRP_Fire_recovery.img" I replaced the "TWRP_Fire_recovery.img" with the TWRP disk image and its failing but I am connected and the device is being recognized. HELP?
Click to expand...
Click to collapse
TWRP can only be used if FireOS was never updated beyond 5.0.1; your device started life at 5.1.x which can not be rolled back to 5.0.x (brick).
FlashFire can be used to flash custom roms and perform other TWRP like functions. Details here. Thoughts:
- use FlashFire 0.50 or above for best results; avoid any versions <0.31
- accept defaults for most flashes (early videos suggested twiddling various options; unnecessary in later builds)
- operations order matters - especially the positioning of Wipe (different for 'clean' and 'dirty' updates)
- avoid 'heavy' GAaps packages; suggest pico, nano, or micro; don't go any higher than mini
- consult ROM OP for specific instructions
Good luck!
Got it already?
There is an awesome tool from the unlocker.
Had also some problems to get it done - 3 times a Bootloop ( Then back to stock) and it finnaly worked on the 4rd try
Here the videos on YT witch helped me (A lot!)
Just a youtube search
1 - General Info
How to install CM12 1 on the Amazon Fire 5th gen Tablet
2 - The Flashing Process via FlashFire
Amazon Fire 5th gen 7in Slim Rom install on Fire OS 5 1 1 with FlashFire App
just use the Unoficial Ford Build from XDA
ROM][UNOFFICIAL] CM-12.1 [14 Jun 2016]
Click to expand...
Click to collapse
also from this thread
- Fresh Installation from FlashFire 0.50
- Click the Red + and choose 'Wipe'
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED
- Click the Red + button and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Cyanogenmod Zip
- Accept defaults
- Click the Red + button again and choose 'Flash ZIP/OTA'
- Navigate to and choose the latest Open Gapps Zip.
- Accept defaults
- Move "Wipe" to the Top of the order
Click to expand...
Click to collapse
Afterwards i also added Wipe Dalvik cache at the end.
Add maybe Su Binary - The FlashFire tool cant handle the implemented root from CM - got stuck with it but i'm happy​
3
How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet
In case you also get a bootloop.
All download links are in the description of the Videos.
The SuperTool is worth Gold.
But get the Rom from the XDA thread
Send you a PM with links - Not allowed because im a Newbie
Hope i could help!
After a long night of research, I finally managed to root my Nexus 6 XT1103 using NRT. I also learned it lets you flash zips without recovery, so I held off installing TWRP in case it created a conflict with the device. Then I selected CM13, OpenGApps aroma, and SuperSU to install in that order. I'm thinking it will bring up the interface to install GApps as usual... but this time there was no interface... no way to tell if anything installed... next thing I know, SuperSU is being flashed... then reboot.
My phone is trying to boot but without GApps it's impossible. Also, I can't get to dev settings to enable USB debugging since I can't even boot. You can yell at me later for not flashing the recovery... but is there anything I can do to save my phone, please? I'm pretty desperate at this point.
Thanks.
EDIT: Never mind. I somehow ended up in this thread and saw this post: https://forum.xda-developers.com/showpost.php?p=55881378&postcount=4
My phone is back to unrooted and factory settings. PHEW. Toolkits for flashing? Never again.
More reading is necessary. Here's a couple of useful links:
https://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
https://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
You'll need to use fastboot. Since you already have NRT installed you provably also have adb and fastboot installed as well.
Basically you'll need to run this command with your phone connected to your computer and in fastboot (bootloader) mode:
Code:
fastboot flash recovery <name-of-twrp-file>
SilverSix said:
After a long night of research, I finally managed to root my Nexus 6 XT1103 using NRT. I also learned it lets you flash zips without recovery, so I held off installing TWRP in case it created a conflict with the device. Then I selected CM13, OpenGApps aroma, and SuperSU to install in that order. I'm thinking it will bring up the interface to install GApps as usual... but this time there was no interface... no way to tell if anything installed... next thing I know, SuperSU is being flashed... then reboot.
My phone is trying to boot but without GApps it's impossible. Also, I can't get to dev settings to enable USB debugging since I can't even boot. You can yell at me later for not flashing the recovery... but is there anything I can do to save my phone, please? I'm pretty desperate at this point.
Thanks.
EDIT: Never mind. I somehow ended up in this thread and saw this post: https://forum.xda-developers.com/showpost.php?p=55881378&postcount=4
My phone is back to unrooted and factory settings. PHEW. Toolkits for flashing? Never again.
Click to expand...
Click to collapse
This is why devs tell people not to use toolkits. You are only doing yourself more harm then good.
Most people wont even reply to a thread if they read you used a tool kit. The nexus is the easiest to do what ever you want/need to do.
I've been sitting around on post-surgery "bedrest" and for whatever reason decided to install a different 7.x ROM using trusty TWRP to try something new. However, I'm stumped as to why no matter what ROM I use I get a successful installation message, but infinite boot animation.
I was running AOKP 7.x and it was stable and happy, and that installation went uneventful.
I've run down a list of possible remedies, like clearing cache, installing GAPPs in order first (no good), after LOS ROM .zip (no good), tried reinstalling AOKP (no good)....
I did make a backup of my phone via TWRP in case of an issue, but even reinstalling the backup did no good. It would load successfully, but upon restart... constant boot animation.
I wiped the SSD clean and tried a fresh install, and according to TWRP it was a success, but I've been watching the LOS boot animation for two hours now.
cRDroid sat in the boot loop all night... a full charge... no joke.
So what are my next steps for getting a working phone? I don't care what ROM I use really... I liked AOKP and just wanted to try something new.
Charlie207 said:
I've been sitting around on post-surgery "bedrest" and for whatever reason decided to install a different 7.x ROM using trusty TWRP to try something new. However, I'm stumped as to why no matter what ROM I use I get a successful installation message, but infinite boot animation.
I was running AOKP 7.x and it was stable and happy, and that installation went uneventful.
I've run down a list of possible remedies, like clearing cache, installing GAPPs in order first (no good), after LOS ROM .zip (no good), tried reinstalling AOKP (no good)....
I did make a backup of my phone via TWRP in case of an issue, but even reinstalling the backup did no good. It would load successfully, but upon restart... constant boot animation.
I wiped the SSD clean and tried a fresh install, and according to TWRP it was a success, but I've been watching the LOS boot animation for two hours now.
cRDroid sat in the boot loop all night... a full charge... no joke.
So what are my next steps for getting a working phone? I don't care what ROM I use really... I liked AOKP and just wanted to try something new.
Click to expand...
Click to collapse
What version TWRP are you using?
The latest custom ROMs require the latest modded TWRP from @bhb27.
Next step would b be to install ROM bare, no GAPPs or anything else. Let it boot successfully. You can always install all the other stuff later.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
What version TWRP are you using?
The latest custom ROMs require the latest modded TWRP from @bhb27.
Next step would b be to install ROM bare, no GAPPs or anything else. Let it boot successfully. You can always install all the other stuff later.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Phone is on TWRP 3.0.2-0_MOD-04
I notice now that v3.2xxxx is out now. Can I use my current TWRP to install the newest .img file to the phone?
I didn't mention that I also attempted to flash the ROM.zip bare a few times for each of the different ROMs I tried to get working. (Both versions of LOS, AOKP , and cRDroid)
Charlie207 said:
Phone is on TWRP 3.0.2-0_MOD-04
I notice now that v3.2xxxx is out now. Can I use my current TWRP to install the newest .img file to the phone?
I didn't mention that I also attempted to flash the ROM.zip bare a few times for each of the different ROMs I tried to get working. (Both versions of LOS, AOKP , and cRDroid)
Click to expand...
Click to collapse
Go to the TWRP thread and get the latest MODDED TWRP. Do NOT use the TWRP from the official site.
I can post a link later if you can't find it, but it's the Quark TWRP thread in the same forum you got some of the other ROMs.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Go to the TWRP thread and get the latest MODDED TWRP. Do NOT use the TWRP from the official site.
I can post a link later if you can't find it, but it's the Quark TWRP thread in the same forum you got some of the other ROMs.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
OK, I'll take a look.
Can I upgrade TWRP within TWRP?
Charlie207 said:
OK, I'll take a look.
Can I upgrade TWRP within TWRP?
Click to expand...
Click to collapse
Yes.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Yes.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
OK.
Successfully upgraded TWRP, and the install of LOS seemed to go smoothly. Now it's back to the waiting game with the install/boot animation. I'll check back in a bit if nothing good has happened.
So after trying to install fresh versions of AOKP and LOS with the most recent version of TWRP I'm still stuck.
Now AOKP (which installs without a hiccup) simply lights up the boot image, and basically shuts off after 20-30 seconds.
Can I get a hint on the best way to completely wipe the phone with TWRP, and trying a different method?
Charlie207 said:
So after trying to install fresh versions of AOKP and LOS with the most recent version of TWRP I'm still stuck.
Now AOKP (which installs without a hiccup) simply lights up the boot image, and basically shuts off after 20-30 seconds.
Can I get a hint on the best way to completely wipe the phone with TWRP, and trying a different method?
Click to expand...
Click to collapse
You can try a truly clean install...
Boot your phone to TWRP, plug into PC, test file transfer. Drag something from PC to Download folder and make sure it's there...
Then, if successful, gather everything you want to install -- ROM, GAPPS, SuperSu, etc. -- onto your PC.
Next save off anything you could not stand to lose or do not have backed up already. Pictures in the DCIM folder, and such.
Now while still in TWRP, format everything on the phone. Including internal storage. You will be completely wiping the phone. You will lose everything on the phone.
Do NOT reboot!
After wiping the phone, while still in TWRP, drag over all the install files you gathered earlier. Install the ROM first and reboot. If successful, go back to TWRP and install GAPPS and whatever else you want.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
You can try a truly clean install...
Boot your phone to TWRP, plug into PC, test file transfer. Drag something from PC to Download folder and make sure it's there...
Then, if successful, gather everything you want to install -- ROM, GAPPS, SuperSu, etc. -- onto your PC.
Next save off anything you could not stand to lose or do not have backed up already. Pictures in the DCIM folder, and such.
Now while still in TWRP, format everything on the phone. Including internal storage. You will be completely wiping the phone. You will lose everything on the phone.
Do NOT reboot!
After wiping the phone, while still in TWRP, drag over all the install files you gathered earlier. Install the ROM first and reboot. If successful, go back to TWRP and install GAPPS and whatever else you want.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
I've done this several times as you describe it. Each time (no matter which ROM) it installs a-ok and then hangs up on the first boot animation.
If TWRP isn't going to work, is there another way to install a .zip? I seem to remember doing it via ADB a few years ago.
Charlie207 said:
I've done this several times as you describe it. Each time (no matter which ROM) it installs a-ok and then hangs up on the first boot animation.
If TWRP isn't going to work, is there another way to install a .zip? I seem to remember doing it via ADB a few years ago.
Click to expand...
Click to collapse
There's ways to push over files via ADB, as this was necessary before TWRP could handle drag and drop. I don't know of any way to flash (install) zipped files via ADB.
Maybe someone else has some ideas?
I know you want latest custom ROM. But as an experiment have you tried flashing back to stock Marshmallow? Pure stock Marshmallow? If that works, then you can try to upgrade back to custom ROMs.
ChazzMatt said:
There's ways to push over files via ADB, as this was necessary before TWRP could handle drag and drop. I don't know of any way to flash (install) zipped files via ADB.
Maybe someone else has some ideas?
I know you want latest custom ROM. But as an experiment have you tried flashing back to stock Marshmallow? Pure stock Marshmallow? If that works, then you can try to upgrade back to custom ROMs.
Click to expand...
Click to collapse
I haven't tried flashing a pure stock MM ROM yet, but will surely give that a try. Do you have a link to a recommended MM ROM?
And, I assume I'd be attempting the install just like I did previously.... e.g. wipe everything, DO NOT reboot, drag .zip from laptop to phone via USB cable, install, (then profit?).
Not that it should matter from a hardware point of view, but I'm using a 2011 MacBook Pro 15" running the latest beta version of OS 10.13.whatever. It sends files to the phone via the Android File Transfer app. I think that's the only way to physically send files from a Mac to Android.
Looking back at some past post of mine, I had a similar issue with cRDroid, which installed it's own recovery software, and wouldn't work with TWRP. I did end up (through serious trial and error headbanging) succeeding in using ADB commands via Terminal to get the phone wiped clean and installed TWRP. After that I was able to load custom ROMs via TWRP and had no problems swapping between different ROMs until just the other day.
I found this ROM, and will attempt to flash it via TWRP: https://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234
Charlie207 said:
I found this ROM, and will attempt to flash it via TWRP: https://forum.xda-developers.com/droid-turbo/development/rom-mpg24-107-70-2-brazilian-6-0-1-t3426234
Click to expand...
Click to collapse
Well **** me running....
That worked. I followed the identical wipe+install procedure for the "stock" MM 6.0.1 ROM as I had for three other 7.x ROMs, and it installed with no issues this time. I'm staring at the Welcome screen, and pretty frustrated that this was the only way to get the phone working again. I'll do a basic setup, and then see if I can flash a 7.x ROM
Thanks for your help in solving this riddle up to now. I'll see what happens....
EDIT: Now that I think of it, the only thing I did different was that, after downloading the ROM to my laptop, I edited the file name from that long name to MM6.0.1.zip so I could simply recognize it faster when clicking between windows and stuff. Other than that I followed the same installation process as noted before.
I'm going to edit/shorten the filename of the LOS ROM and see if removing unneeded characters does anything.
Nothing is working. The Brazilian stock MM ROM works, in a basic sense, but doesn't allow calls or WiFi, so that's kind of a moot point.
Back to the drawing board.
The Brazilian MM ROM was junk for my purposes, but the other MM ROM worked.. Phone is setting up now. WiFi and LTE work on it, so I guess I'll be stuck with 6.x for a while until I feel like messing around with a 7.x ROM.
Charlie207 said:
Nothing is working. The Brazilian stock MM ROM works, in a basic sense, but doesn't allow calls or WiFi, so that's kind of a moot point.
Back to the drawing board.
Click to expand...
Click to collapse
The Brazilian ROM needs your own modem. You would need to flash that in TWRP separately.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
The Brazilian ROM needs your own modem. You would need to flash that in TWRP separately.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Yeah... I realized my mistake, and flashed the other MM ROM. That one works normally.
I'm stumped why all of a sudden 7.x ROMs refuse to install on my phone. I had prevously installed crDroid, AOKP, and RR 7.x ROMs just fine via TWRP.
ChazzMatt said:
There's ways to push over files via ADB, as this was necessary before TWRP could handle drag and drop. I don't know of any way to flash (install) zipped files via ADB.
Maybe someone else has some ideas?...
Click to expand...
Click to collapse
I'm not sure if all TWRP versions for different devices are the same, but with my Pixel C (TWRP 3.2.1) there is an "adb sideload" option in recovery to install zip files via adb from a computer.
I think the command is: adb sideload filenamegoeshere.zip
Sorry for reviving this thread, but I have exact same issue. Stock Lollipop and MM roms work, but any custom rom just hangs on boot animation forever did you manage to sort it out? @Charlie207