I tried so many sites but I can't get firmware from anywhere please give me a link to firmware for 128gb 8gb ram device and please provide a decent guide to flash it without losing imei number... I'm counting on someone to respond.
Rmx1807? You are lucky to be able to flash via qfil!
sasrev0 said:
I tried so many sites but I can't get firmware from anywhere please give me a link to firmware for 128gb 8gb ram device and please provide a decent guide to flash it without losing imei number... I'm counting on someone to respond.
Click to expand...
Click to collapse
I faced a similar issue while I was trying to flash a GSI ROM onto my Realme 2 Pro (4GB variant). I ended up with a soft brick (i.e., I was able too boot into the bootloader, as well as the custom TWRP Recovery I had installed). Somehow, I ended up losing my Stock ColorOS as well. None of the GSI ROMs I tried worked (actually, 2 did boot up, and crashed almost immediately). Also, when in the TWRP Recovery, I could access my phone's memory from my laptop (this is an important piece of information in solving this problem).
As a last ditch attempt, I somehow found a YouTube video which provided some assistance of sorts (being a new user I'm afraid I can not provide the link to it, but you can go to the Realme Community website and search for 'Ubrick', and open the thread titled 'How to install stock color os ROM, unroot, Unbrick, rooted, lock bootloader on realme 2 pro' where the video link will be provided).
Now my phone is up and running the Stock ColorOS, thankfully.
I'll explain the steps as clearly as I can.
1. Went to the Realme website, and downloaded the official software from there.
2. Put in a microSD card into my phone, and plugged the phone into my laptop.
3. Turned on the phone and it immediately loaded the bootloader. Using fastboot, I erased the system. And then loaded the recovery.
3. Once TWRP booted up, I accessed the microSD card storage from my laptop, and transferred the copy of the ColorOS Stock Recovery img (again, being a new user, I can't put a link, but the YouTube video has the link in the description) onto the same, and the transferred the Stock ColorOS ozip file that I had downloaded.
4. On my phone, on TWRP, went to 'Install' and changed storage to microSD, and selected 'Install Image'. When the ColorOS Stock Recovery img showed up, I installed the same.
5. Instead of hitting 'Reboot' directly, I went back to the home screen of TWRP, and went into 'Reboot' and hit 'Recovery'. Now is when another problem cropped up for me. It hung on the screen. So I did a manual restart, directly into the bootloader (pressing Power Button+Volume Down Button).
6. When the bootloader loaded up once more, I rebooted into recovery from there.
7. The Stock ColorOS Recovery opened up. I pressed the first option (Install from Storage Device). I selected the microSD option. The ozip version of the Stock ColorOS 5.2 for version RMX1801EX_11.A.15 showed up. I pressed on that option, and some message popped up (excuse me for not remembering, as I was literally on my last leg at this time). I dismissed the option, and it the installation started.
8. Soon after, a reboot option popped up, for which I hit yes. The phone rebooted, and it booted up as a whole new phone, without a problem. Of course the bootloader unlock was removed (I presume, because the red blinking error that was present is not there; and my software shows that it is up to date)
This is possibly not the best solution, but it worked for me. Do note that when I had saved the ozip file directly on my phone before the whole process, I could not access it, for some reason.
I hope this helps!
Thanks a lot man
batflashholmes said:
I faced a similar issue while I was trying to flash a GSI ROM onto my Realme 2 Pro (4GB variant). I ended up with a soft brick (i.e., I was able too boot into the bootloader, as well as the custom TWRP Recovery I had installed). Somehow, I ended up losing my Stock ColorOS as well. None of the GSI ROMs I tried worked (actually, 2 did boot up, and crashed almost immediately). Also, when in the TWRP Recovery, I could access my phone's memory from my laptop (this is an important piece of information in solving this problem).
As a last ditch attempt, I somehow found a YouTube video which provided some assistance of sorts (being a new user I'm afraid I can not provide the link to it, but you can go to the Realme Community website and search for 'Ubrick', and open the thread titled 'How to install stock color os ROM, unroot, Unbrick, rooted, lock bootloader on realme 2 pro' where the video link will be provided).
Now my phone is up and running the Stock ColorOS, thankfully.
I'll explain the steps as clearly as I can.
1. Went to the Realme website, and downloaded the official software from there.
2. Put in a microSD card into my phone, and plugged the phone into my laptop.
3. Turned on the phone and it immediately loaded the bootloader. Using fastboot, I erased the system. And then loaded the recovery.
3. Once TWRP booted up, I accessed the microSD card storage from my laptop, and transferred the copy of the ColorOS Stock Recovery img (again, being a new user, I can't put a link, but the YouTube video has the link in the description) onto the same, and the transferred the Stock ColorOS ozip file that I had downloaded.
4. On my phone, on TWRP, went to 'Install' and changed storage to microSD, and selected 'Install Image'. When the ColorOS Stock Recovery img showed up, I installed the same.
5. Instead of hitting 'Reboot' directly, I went back to the home screen of TWRP, and went into 'Reboot' and hit 'Recovery'. Now is when another problem cropped up for me. It hung on the screen. So I did a manual restart, directly into the bootloader (pressing Power Button+Volume Down Button).
6. When the bootloader loaded up once more, I rebooted into recovery from there.
7. The Stock ColorOS Recovery opened up. I pressed the first option (Install from Storage Device). I selected the microSD option. The ozip version of the Stock ColorOS 5.2 for version RMX1801EX_11.A.15 showed up. I pressed on that option, and some message popped up (excuse me for not remembering, as I was literally on my last leg at this time). I dismissed the option, and it the installation started.
8. Soon after, a reboot option popped up, for which I hit yes. The phone rebooted, and it booted up as a whole new phone, without a problem. Of course the bootloader unlock was removed (I presume, because the red blinking error that was present is not there; and my software shows that it is up to date)
This is possibly not the best solution, but it worked for me. Do note that when I had saved the ozip file directly on my phone before the whole process, I could not access it, for some reason.
I hope this helps!
Click to expand...
Click to collapse
Though I ended up going to service center and got it started with wasting a lot money as it seemed only option available, at least now I know if I ever lose stock rom again there's other way. Thanks!
There is a guide flashing stock ROM from following site https://www.getdroidtips.com/stock-rom-on-oppo-realme-2-pro-firmware/
I don't have any issues with my device so I do not intent to test it, do it at your own risk.
need some help
Need a help.
3. Using fastboot, I erased the system. And then loaded the recovery. (how to do that ?)can we fastboot flash stock recovery ? why erased system?
sasrev0 said:
Though I ended up going to service center and got it started with wasting a lot money as it seemed only option available, at least now I know if I ever lose stock rom again there's other way. Thanks!
Click to expand...
Click to collapse
batflashholmes said:
I faced a similar issue while I was trying to flash a GSI ROM onto my Realme 2 Pro (4GB variant). I ended up with a soft brick (i.e., I was able too boot into the bootloader, as well as the custom TWRP Recovery I had installed). Somehow, I ended up losing my Stock ColorOS as well. None of the GSI ROMs I tried worked (actually, 2 did boot up, and crashed almost immediately). Also, when in the TWRP Recovery, I could access my phone's memory from my laptop (this is an important piece of information in solving this problem).
As a last ditch attempt, I somehow found a YouTube video which provided some assistance of sorts (being a new user I'm afraid I can not provide the link to it, but you can go to the Realme Community website and search for 'Ubrick', and open the thread titled 'How to install stock color os ROM, unroot, Unbrick, rooted, lock bootloader on realme 2 pro' where the video link will be provided).
Now my phone is up and running the Stock ColorOS, thankfully.
I'll explain the steps as clearly as I can.
1. Went to the Realme website, and downloaded the official software from there.
2. Put in a microSD card into my phone, and plugged the phone into my laptop.
3. Turned on the phone and it immediately loaded the bootloader. Using fastboot, I erased the system. And then loaded the recovery.
3. Once TWRP booted up, I accessed the microSD card storage from my laptop, and transferred the copy of the ColorOS Stock Recovery img (again, being a new user, I can't put a link, but the YouTube video has the link in the description) onto the same, and the transferred the Stock ColorOS ozip file that I had downloaded.
4. On my phone, on TWRP, went to 'Install' and changed storage to microSD, and selected 'Install Image'. When the ColorOS Stock Recovery img showed up, I installed the same.
5. Instead of hitting 'Reboot' directly, I went back to the home screen of TWRP, and went into 'Reboot' and hit 'Recovery'. Now is when another problem cropped up for me. It hung on the screen. So I did a manual restart, directly into the bootloader (pressing Power Button+Volume Down Button).
6. When the bootloader loaded up once more, I rebooted into recovery from there.
7. The Stock ColorOS Recovery opened up. I pressed the first option (Install from Storage Device). I selected the microSD option. The ozip version of the Stock ColorOS 5.2 for version RMX1801EX_11.A.15 showed up. I pressed on that option, and some message popped up (excuse me for not remembering, as I was literally on my last leg at this time). I dismissed the option, and it the installation started.
8. Soon after, a reboot option popped up, for which I hit yes. The phone rebooted, and it booted up as a whole new phone, without a problem. Of course the bootloader unlock was removed (I presume, because the red blinking error that was present is not there; and my software shows that it is up to date)
This is possibly not the best solution, but it worked for me. Do note that when I had saved the ozip file directly on my phone before the whole process, I could not access it, for some reason.
I hope this helps!
Click to expand...
Click to collapse
batflashholmes said:
I faced a similar issue while I was trying to flash a GSI ROM onto my Realme 2 Pro (4GB variant). I ended up with a soft brick (i.e., I was able too boot into the bootloader, as well as the custom TWRP Recovery I had installed). Somehow, I ended up losing my Stock ColorOS as well. None of the GSI ROMs I tried worked (actually, 2 did boot up, and crashed almost immediately). Also, when in the TWRP Recovery, I could access my phone's memory from my laptop (this is an important piece of information in solving this problem).
As a last ditch attempt, I somehow found a YouTube video which provided some assistance of sorts (being a new user I'm afraid I can not provide the link to it, but you can go to the Realme Community website and search for 'Ubrick', and open the thread titled 'How to install stock color os ROM, unroot, Unbrick, rooted, lock bootloader on realme 2 pro' where the video link will be provided).
Now my phone is up and running the Stock ColorOS, thankfully.
I'll explain the steps as clearly as I can.
1. Went to the Realme website, and downloaded the official software from there.
2. Put in a microSD card into my phone, and plugged the phone into my laptop.
3. Turned on the phone and it immediately loaded the bootloader. Using fastboot, I erased the system. And then loaded the recovery.
3. Once TWRP booted up, I accessed the microSD card storage from my laptop, and transferred the copy of the ColorOS Stock Recovery img (again, being a new user, I can't put a link, but the YouTube video has the link in the description) onto the same, and the transferred the Stock ColorOS ozip file that I had downloaded.
4. On my phone, on TWRP, went to 'Install' and changed storage to microSD, and selected 'Install Image'. When the ColorOS Stock Recovery img showed up, I installed the same.
5. Instead of hitting 'Reboot' directly, I went back to the home screen of TWRP, and went into 'Reboot' and hit 'Recovery'. Now is when another problem cropped up for me. It hung on the screen. So I did a manual restart, directly into the bootloader (pressing Power Button+Volume Down Button).
6. When the bootloader loaded up once more, I rebooted into recovery from there.
7. The Stock ColorOS Recovery opened up. I pressed the first option (Install from Storage Device). I selected the microSD option. The ozip version of the Stock ColorOS 5.2 for version RMX1801EX_11.A.15 showed up. I pressed on that option, and some message popped up (excuse me for not remembering, as I was literally on my last leg at this time). I dismissed the option, and it the installation started.
8. Soon after, a reboot option popped up, for which I hit yes. The phone rebooted, and it booted up as a whole new phone, without a problem. Of course the bootloader unlock was removed (I presume, because the red blinking error that was present is not there; and my software shows that it is up to date)
This is possibly not the best solution, but it worked for me. Do note that when I had saved the ozip file directly on my phone before the whole process, I could not access it, for some reason.
I hope this helps!
Click to expand...
Click to collapse
I tried to flash stock RealMe ROM, downloaded from the official website, from the stock Recovery but it fails! Help.
Recovery Image for RMX1805
Where can I get recovery image for Realme 2 (RMX1805). please someone help.
cant access sd card in color os recovery PLEASE HELP IF YOU CAN
batflashholmes said:
I faced a similar issue while I was trying to flash a GSI ROM onto my Realme 2 Pro (4GB variant). I ended up with a soft brick (i.e., I was able too boot into the bootloader, as well as the custom TWRP Recovery I had installed). Somehow, I ended up losing my Stock ColorOS as well. None of the GSI ROMs I tried worked (actually, 2 did boot up, and crashed almost immediately). Also, when in the TWRP Recovery, I could access my phone's memory from my laptop (this is an important piece of information in solving this problem).
As a last ditch attempt, I somehow found a YouTube video which provided some assistance of sorts (being a new user I'm afraid I can not provide the link to it, but you can go to the Realme Community website and search for 'Ubrick', and open the thread titled 'How to install stock color os ROM, unroot, Unbrick, rooted, lock bootloader on realme 2 pro' where the video link will be provided).
Now my phone is up and running the Stock ColorOS, thankfully.
I'll explain the steps as clearly as I can.
1. Went to the Realme website, and downloaded the official software from there.
2. Put in a microSD card into my phone, and plugged the phone into my laptop.
3. Turned on the phone and it immediately loaded the bootloader. Using fastboot, I erased the system. And then loaded the recovery.
3. Once TWRP booted up, I accessed the microSD card storage from my laptop, and transferred the copy of the ColorOS Stock Recovery img (again, being a new user, I can't put a link, but the YouTube video has the link in the description) onto the same, and the transferred the Stock ColorOS ozip file that I had downloaded.
4. On my phone, on TWRP, went to 'Install' and changed storage to microSD, and selected 'Install Image'. When the ColorOS Stock Recovery img showed up, I installed the same.
5. Instead of hitting 'Reboot' directly, I went back to the home screen of TWRP, and went into 'Reboot' and hit 'Recovery'. Now is when another problem cropped up for me. It hung on the screen. So I did a manual restart, directly into the bootloader (pressing Power Button+Volume Down Button).
6. When the bootloader loaded up once more, I rebooted into recovery from there.
7. The Stock ColorOS Recovery opened up. I pressed the first option (Install from Storage Device). I selected the microSD option. The ozip version of the Stock ColorOS 5.2 for version RMX1801EX_11.A.15 showed up. I pressed on that option, and some message popped up (excuse me for not remembering, as I was literally on my last leg at this time). I dismissed the option, and it the installation started.
8. Soon after, a reboot option popped up, for which I hit yes. The phone rebooted, and it booted up as a whole new phone, without a problem. Of course the bootloader unlock was removed (I presume, because the red blinking error that was present is not there; and my software shows that it is up to date)
This is possibly not the best solution, but it worked for me. Do note that when I had saved the ozip file directly on my phone before the whole process, I could not access it, for some reason.
I hope this helps!
Click to expand...
Click to collapse
whenever i try to mount sd card in color os it doesn't show anything and i can't install stock rom using trwp please help
Guys dont worry about the firmware file
visit this link to get every firmware for free here
Flash File: Download For All Mobile, Firmware File (Stock ROM) - Mobile Guru4
Flash File Download For all Android Mobile Phone. Here the Official Original Firmware File (Stock ROM) of all smartphones are available.
www.mobileguru4.com
Related
Hi folks,
I recently rooted by N4. It was running Android 5.0.
I also have MultiROM installed, with CyanogenMod installed as a secondary ROM.
I didn't realise I couldn't apply the OTA updates to the stock Android system (my oversight), and I allowed the device to download and (attempt an) the recent 5.0.1 update from Google.
When the update attempted to reboot the device, I could see in the terminal data that popped up, that it failed.
After that device now gets stuck in the booting stage with the little coloured balls drifting around.
I continued to use my phone with the secondary ROM (Cyanogen) for some days until I had time to sort this out.
MY ATTEMPTED RECOVERY
I read that ordinarily on a rooted device one would manually apply the various image files from the full 5.0.1 package.
So, following instructions found here: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Using method two (long method).
... In fastboot mode I flashed the system, boot, recovery, cache (after clearing cache), radio images from the 5.0.1 stock image.
At first I didn't flash the bootloader (as I wanted to maintain the multiboot loader I had installed) nor the user.img (I don't want to lose my user data). I read this should work. But it didn't.
When it came to booting into recovery mode to finish the process, an android icon with a ! warning on it would appear, and I could not do the recovery.
So, I have since flashed the bootloader also. That didn't change much, except that my dual-boot boot loader is now gone, and the device is still not recoverable.
Is there something I am not doing correctly? How can I recover this device so that it has 5.0.1, my existing user data, and my existing dual boot bootloader?
Cheers,...
May have solved it...
I'll post another update in a moment. Posting this just in case someone starts responding to my question in the interim.
After further fiddling around, I may have resolved this issue. I've managed to get it into recovery menu, rebooted from there, and device is now in "Android is updating" mode. Looking good.
Will post new message soon as to whether this was successful or not.
Issues continue
So, after the device booted a screen appeared for a fraction of a second, that appeared to be the screen for selecting system language (as per what happens when a device is first run after a clean install). But the screen almost instantly goes black except for the little network icon and battery icon and time in the top right of the screen.
If I use the power button to lock the screen and again to activate it, the screen very briefly flashed up the language selector, then goes blank again.
So... it seems something odd is happening after applying the 5.0.1 file.
Any suggestions?
Flash the 5.0.1 factory image with fastboot
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Flash the 5.0.1 factory image with fastboot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well, this is what I resorted to doing. And it worked. Phone started and was as new. Of course, I lost my user data which is a ****. I did pull the SDCARD content over ADB, but am not sure how I'd go about pushing it all back on, into right locations, etc.
BUT—and it's a BIG BUT—when I re-rooted it and applied SuperSu, it couldn't be put into recovery mode any more. It would keep running through the SuperSu install process each time I'd attempt to go into Recovery.
I ended up ignoring this, and installing Busybox (with Play) and SuperSu.apk (via Play). But the SuperSU apk would keep saying its files needed to be installed/updated.
I forget the exact mess that unfolded, but eventually (after installing MultiROM) I could boot the phone as it would ALWAYS go into (custom) recovery.
So I starter the whole process again, with another clean install of 5.0.1, and yet now it is stuck at the bootloader (the little swirling balls screen).
AndroidWelcome said:
Well, this is what I resorted to doing. And it worked. Phone started and was as new. Of course, I lost my user data which is a ****. I did pull the SDCARD content over ADB, but am not sure how I'd go about pushing it all back on, into right locations, etc.
BUT—and it's a BIG BUT—when I re-rooted it and applied SuperSu, it couldn't be put into recovery mode any more. It would keep running through the SuperSu install process each time I'd attempt to go into Recovery.
I ended up ignoring this, and installing Busybox (with Play) and SuperSu.apk (via Play). But the SuperSU apk would keep saying its files needed to be installed/updated.
I forget the exact mess that unfolded, but eventually (after installing MultiROM) I could boot the phone as it would ALWAYS go into (custom) recovery.
So I starter the whole process again, with another clean install of 5.0.1, and yet now it is stuck at the bootloader (the little swirling balls screen).
Click to expand...
Click to collapse
Try a full wipe from Factory Recovery, and see if it will fix the bootloop.
Bootloop no more...
ariesgodofwar said:
Try a full wipe from Factory Recovery, and see if it will fix the bootloop.
Click to expand...
Click to collapse
(wiping the sweat from his brow...)
After many tedious hours of messing around with this beast... there is life beyond the bootloop.
Back to a stock install.
So, now I am wondering why the SuperSu/Root process didn't work on my last round on this.
The SuperSu installer would kick in EVERY time I went into Recovery mode, and would then reboot the phone. This made it impossible to do things with ADP because I essentially couldn't get into recovery mode. I wanted to push through some of the stuff I pulled using ADP before I wiped the phone previously.
I installed MultiROM (which includes TWRP [is that what it's called] recovery system. BUT then go stuck in a Recovery loop.
Not wishing to repeat that fiasco... does anyone more knowledgeable than I (not a difficult status to achieve) have any suggestions to what might have caused those issues?
I decided to finally root my Wifi only Galaxy Tab 4, 16 gig. To my understanding it is the T330. It had the latest OTA - 5.1.1 I believe?
After installing TWRP and trying to flash SuperSU it won't boot past the Samsung logo.
I did the following:
Prior to today I have had the USB drivers installed
Downloaded and extracted ODIN 3.0.9
Downloaded TWRP 2.8.7 Tar file for the T3xx series
Downloaded SuperSU zip file for version 2.46
I opened up ODIN, unchecked the "Auto Reboot" box (after seeing elsewhere that it was needed when flashing the recovery), checked the box for "AP" and selected the .tar file for TWRP. I clicked start, everything went correctly, I removed the USB cable and manually restarted the device by holding the power button. Once it was off I then held the power button, volume up, and home button to boot into recovery, and to my excitement I was greeted with TWRP. So far it looked like it was going according to plan. A screen came up saying that the system was currently read only, and it was giving me the choice to allow the recovery to change it. I swiped to allow it to change it so the system partitions were not read only. I went to the install option, and selected the SuperSU zip file. Installed it, it said that it installed correctly. I went back to the main menu and rebooted the device. That's when things did NOT go according to plan. It played the nice little boot sound, the animated Samsung logo came up, and I waited. I waited some more. I continued to wait. After 10 minutes of the Samsung animation repeating I assumed that trouble was afoot and turned the tablet off and attempted to get back into recovery, which it did. I then turned it off and checked to see if I could still get into Download Mode: and it can and the PC can see it as connected when I load up ODIN.
So I have the tablet soft bricked. My goal was to have it rooted with custom recovery to install roms.
If that's not possible, I assume my best bet would be to use ODIN to push the Samsung files over and flash it back to factory that way, undoing what I have done?
Any advice would be greatly appreciated. I tried to be as detailed as possible to assist anyone who may be willing to help.
SebringTech said:
I decided to finally root my Wifi only Galaxy Tab 4, 16 gig. To my understanding it is the T330. It had the latest OTA - 5.1.1 I believe?
After installing TWRP and trying to flash SuperSU it won't boot past the Samsung logo.
I did the following:
Prior to today I have had the USB drivers installed
Downloaded and extracted ODIN 3.0.9
Downloaded TWRP 2.8.7 Tar file for the T3xx series
Downloaded SuperSU zip file for version 2.46
I opened up ODIN, unchecked the "Auto Reboot" box (after seeing elsewhere that it was needed when flashing the recovery), checked the box for "AP" and selected the .tar file for TWRP. I clicked start, everything went correctly, I removed the USB cable and manually restarted the device by holding the power button. Once it was off I then held the power button, volume up, and home button to boot into recovery, and to my excitement I was greeted with TWRP. So far it looked like it was going according to plan. A screen came up saying that the system was currently read only, and it was giving me the choice to allow the recovery to change it. I swiped to allow it to change it so the system partitions were not read only. I went to the install option, and selected the SuperSU zip file. Installed it, it said that it installed correctly. I went back to the main menu and rebooted the device. That's when things did NOT go according to plan. It played the nice little boot sound, the animated Samsung logo came up, and I waited. I waited some more. I continued to wait. After 10 minutes of the Samsung animation repeating I assumed that trouble was afoot and turned the tablet off and attempted to get back into recovery, which it did. I then turned it off and checked to see if I could still get into Download Mode: and it can and the PC can see it as connected when I load up ODIN.
So I have the tablet soft bricked. My goal was to have it rooted with custom recovery to install roms.
If that's not possible, I assume my best bet would be to use ODIN to push the Samsung files over and flash it back to factory that way, undoing what I have done?
Any advice would be greatly appreciated. I tried to be as detailed as possible to assist anyone who may be willing to help.
Click to expand...
Click to collapse
Have you tried wiping dalvik and cache through recovery? If that doesn't help maybe do a factory reset before restoring the factory image?
Sent from my SM-T330 using Tapatalk
Edit: I think this might be what you need
http://forum.xda-developers.com/showthread.php?t=3176668
I tried to wipe cache and dalvik - still gets stuck at the Samsung logo... Tried to do a factory reset from TWRP and after rebooting from recovery it continues to get stuck. I'll try flashing the kernel but I don't understand why that would have gotten messed with from flashing the recovery and installing the SuperSU part.
Okay I take back my statement... flashed the kernel, after flashing did a cache and dalvik wipe and boom... it boots!!! You are officially my hero! Thank you!
SebringTech said:
Okay I take back my statement... flashed the kernel, after flashing did a cache and dalvik wipe and boom... it boots!!! You are officially my hero! Thank you!
Click to expand...
Click to collapse
You're very welcome. Good luck.
Sent from my SM-T330 using Tapatalk
CM Installation Problems
I posted this last night on the CM forums and have had one responder but thought this might reach a wider audience. I'm copying and pasting the OP and I'll try to include as much info as possible.
Hi,
I'm fairly new to flashing etc. New as in this was the first time I tried it. I'm fairly tech savvy, I just haven't flashed a custom rom before.
I followed all the instructions on the CM wiki for the S5 (AU).
Long story short, every step in those instructions worked perfectly once I accounted for my own errors or misunderstandings. Flashed the TWRP recovery just fine. There were problems with ADB not working when the phone was in recovery mode (discovered it's something to do with win 8 and above) so I just rebooted into stock rom (where ADB worked) and used adb push to copy the files to sdcard. Everything went swimmingly until the actual CM installation. I followed the instructions and did the factory reset, went to install and the installation took something like 10 mins before I started to wonder how long it was meant to take. Little bit of googling got me more worried, after about 20 I pulled the battery, back into recovery and went into Wipe again. Cleared Dalvik, cache, system all manually and then did the factory reset option on top of that just to be thorough. Installation is still taking forever. It's currently been around 20 minutes. Some posts I've read say rooting is required but that installation article specifically says rooting is neither required nor recommended. I've no idea where to turn now. I can't use ADB to copy a stock firmware back on as it doesn't work in recovery mode, nor can I try the klte or kltedev versions (don't think they're meant for this model anyway). It's just stuck on "flashing file 1 of 1" - the last thing in the log is "Patching system image unconditionally..." I'm running windows 10, not that that should make any difference.
Any help would be hugely appreciated.
Update: After about 40 mins I pulled battery again and thought I'd try booting normally and seeing what it does. Just sits at "Samsung Galaxy S5" splash screen.
TL;DR/Extra info:
Galaxy S5 G900I (AU) Vodafone
Was running Lollipop 5.0 as per Vodafone OTA update
Using instructions on the CM wiki page for the GS5 (AU) I flashed TWRP using Heimdall with no errors. ADB would not work in download/recovery (couldn't see device) so booted phone into stock ROM and used ADB push to copy the CM file to sdcard root. Note: I don't have an sd card, it's internal storage. Rebooted into recovery, tried to flash CM, it sat on installation screen for about 20 mins. Tried 3 times, leaving it for 40 mins, still nothing. Stock OS has been wiped so I can't get back into that, and because ADB doesn't work I can't reflash recovery from scratch, can't copy a new download of CM on, can't copy the stock ROM to flash. ADB Sideload just tries to run and fails. Currently trying to get ADB working. Running Win 10, device stopped showing up in device manager or Zadig at this point. Restarted PC, ran Zadig again, it saw device, reinstalled driver, now shows up in device manager under USB Devices as MSM8960 (so not under Portable Devices as it once did). Note: the safely remove icon in system tray showed "Galaxy S5 (Phone name)" before I ran Zadig again, now it shows MSM8960.
Help
Reflashed TWRP with Heimdall. Didn't change a thing.
After the biggest headache of my life I got ADB working in TWRP. Had to modify the .inf of the google usb driver that the SDK installs and add the hardware ID of the device in recovery mode. Apparently the ID changes when in recovery so the driver doesn't recognise it anymore. Success!
I downloaded the nightly from 30/09, renamed it update.zip so the filename was simpler, pushed it with ADB to sdcard and am now trying to install it. So far same issue, but at least I can push files to the phone now. It definitely seems to be an issue with the install process.
Update: Still same issue. New zip, new build, reflashed recovery and still hangs on install. Would trying ClockWorkMod be worth it rather than TWRP?
When sideloading the ROM and viewing command prompt on the PC everything works fine until it hits 90% and then it stops suddenly and stays there. During the TWRP factory reset it also says unable to mount system several times if that's any help
I've now tried flashing Philz Touch and given that a go. Factory reset/wiping seemed to run with less of a hitch but still exactly the same deal, gets to "patching system unconditionally" when installing CM and just sits there, progress bar doesn't even fill up a bit. I'm stumped.
Ok, so I've been Resurrection_Remix_LP_v5.4.6-20150530-hlte.zip for quite some time now, probably since not long after it's release, and it pretty much liked it. Except for the occasional seemingly random "auto reset" of android/app settings and preference (such as forgetting all my saved wifi ssid) after a random crash/reboot.
Starting last week, the camera became problematic, often failing to start entirely (error message, "could not connect to to camera"), or could connect to the back camera, but freezes when i try to switch to front camera. I tried wiping data with TitBak and it worked again, but the problem comes back a while later. Is this a software or hardware problem?
Anyway, I finally decided to upgrade the the latest RR and wanted to upgrade TWRP from 2.8.5 as I go along. Since the existing version fits the requirement for TWRP install...
Code:
TWRP Install (Requires TWRP 2.8.4 or higher already installed):
Download the latest TWRP image file (.img) from the download link and boot TWRP. Go to install and find and select the Images... button. Browse to the image that you downloaded and select it. Choose recovery and swipe to flash.
... I went ahead and did it, with the standard 3 wipes (couple of times) and then the recovery flash. Turns out it didn't work and the phone just keeps freezing at the first screen with Note3 logo and the red/blue/yellow test at the top left saying booting to recovery. It never did!
I then tried to reflash the recovery using odin with the .tar file, it flashed fine and auto re-booted back into the launcher (everything's gone of course). But I still needed to go back into recovery mode to either flash a higher version of TWRP, or install the newer RR.
Still, it gets stuck and wont go to recovery no matter i used the hardware button method, or recovery button in the power menu, or adb reboot recovery.
What's wrong!?!??!
c'mon guys, give me something.
You have flashed newer RR how it goes back to older version after you odin twrp?. Or you mean currently it's the latest, just in the future you need to update to the newest?. Did you flashed the correct rom zip for your phone?. I mean hlte for n9005 and the rest for other variants. I haven't flash 'google like' roms for long not sure it's still different zip for each variants.
Sent from my SM-N920C
I haven't even got to the point of flashing the ROM so it's still on the old RR.
I need to know how to upgrade to the latest TWRP first.
Then why 3 wipes?. If you wipe system you have no rom in the phone.
Sent from my SM-N920C
It's been a year already since I checked this sub and I am still using the TWRP that flickers and is chinese. Is there like an upgraded version for our device? Specifically for the non elite variant US version?
I think I might have screwed my phone because after I flashed a new rom(RR) my internal storage won't mount on recovery and when I connect it to pc. But I can see it in my phone when I'm on system(thank god) This is weird because I have not put any security lock on my phone before backing it up. So I am assuming that I need to update my TWRP to something latest to solve this issue, but I haven't been keeping up to this sub, i don't know if there's a newer compatible of TWRP.
And I also forgot why I did not went with the official one from TWRP. Maybe because it messes up the bootloader? or something like that, forgot since it's been a year already and I remember reading into a guide to use the chinese twrp.
[Solved]
If this happens to your device and you happen to use the chinese screen flicker fest TWRP, just go on and flash the latest official TWRP for our device. And you're going to be able to see your internal storage again.
you can either flash it ADB or from your recovery, but I flashed mine through TWRP
drckml said:
It's been a year already since I checked this sub and I am still using the TWRP that flickers and is chinese. Is there like an upgraded version for our device? Specifically for the non elite variant US version?
I think I might have screwed my phone because after I flashed a new rom(RR) my internal storage won't mount on recovery and when I connect it to pc. But I can see it in my phone when I'm on system(thank god) This is weird because I have not put any security lock on my phone before backing it up. So I am assuming that I need to update my TWRP to something latest to solve this issue, but I haven't been keeping up to this sub, i don't know if there's a newer compatible of TWRP.
And I also forgot why I did not went with the official one from TWRP. Maybe because it messes up the bootloader? or something like that, forgot since it's been a year already and I remember reading into a guide to use the chinese twrp.
Click to expand...
Click to collapse
Stop reading out of date articles, and use the latest Twrp here: https://twrp.me/leeco/leecolepro3.html
The Chinese bootloader issue is no longer an issue
* So to be clear about you issue you cannot boot to recovery.
* You do see you phone when you connect it to the computer...Right?
* BTW, I also have an X727
Your issue is most likely due to corruption and encryption
Backup whatever data you can and then use the All in One ( "AIT " ) tool to remove encryption ( NOTE: this is going to erase your data.
Next Using AIT install Twrp and magisk 17.1 or the easier way to resolve this may be to temporarily go back to stock.
Option 1
Try flashing the latest Twrp and magisk 17.1, using either ADB or AIT
After flashing boot into TWRP recovery
1. Go to "Wipe" and then to "Advanced Wipe".
2. Mark "Dalvik / ART Cache", "System", "Data" and "Cache".
3. "Swipe to Wipe" and proceed back the main menu.
4. Go to "Install".
5. Select the ROM zip file and then press "Add more Zips" and select the Gapps zip file, and then the Magisk file.
6. "Swipe to confirm Flash" and wait for some time.
7. After the flashing is finished, just reboot to recovery, check boxes to keep Twrp installed
8. Boot to system go through setup.
Option 2
You could flash my Recovery which includes Twrp and Root. ( Instructions at Link Below)
Afterwards you will be able to update the Twrp, and Root, then Flash whatever you want.
Le Eco Pro 3 X727 Twrp Backup : Clean Full Stock X727 recovery EUI 5.8.21s
https://forum.xda-developers.com/showpost.php?p=75021582
Option 3
Use All in One tool to restore my recovery, Flash a Stock Rom , or simply Flash TWRP/ROOT and then your Rom> Gapps> Magisk once again > Reboot to Recovery ( Check Boxes, for Twrp manager installation) Reboot to recovery > do not choose to make you drive read only! Clear Cache ( Not Dalvik) Reboot to system > Finished.
However, there is a faster way: @mauronofrio created a tool called: "TOOL ALL IN ONE"" and its great!
https://forum.xda-developers.com/and...ctory-t3358711
Its an excellent tool for keeping your drivers and adb up to date. Plus it will give ADB system wide privileges.
Mauronofrio's tool can also unencrypt your storage
After install the All in One Tool
Make sure to check for the AIT program for updates, to the tool itself and to ADB.
Next, click button to allow ADB privileges system wide.
Get more information here:*https://toolaio.tk**
XDA page for Le pro 3 : https://forum.xda-developers.com/le-...1#post71627491
* The all is one tool is excellent and you can use it to install everything you want.
* You can use it to unlock the bootloader.
* Remove Encryption
* Install TWRP,
* Install your Rom, Gapps and Magisk etc.
* The tool will also update your existing installation of ADB, Android Drivers, and provide system wide ADB privileges.
Of course use ADB or AIT once the phone is restored but you would be better off buying an OTG adapter and a USB 3.0 USB Flash drive. This way you can quickly make changes on the fly. I recommend buying at least 32GB usb 3.0 drive. Absolutely, the OTG adapter is the best method, because you will have all of your files available for quick installation and you can make numerous nandroid backups of your favorite rom installations. So If you get bored with one Rom, you can quickly restore another Rom in 5 to 10 minutes.
Again , if you do not use an OTG drive. Just use ADB or AIT for flashing your files, the steps are same as with any other phone.
Finally, look past any typos, I don't have time to proofread after spending so much time on a single post.
Thanks for the detailed response!
my issue was, I can go to recovery but it is not mounting my internal storage. It was showing as 0mb. I am aware that this is usually happens when you encrypt your device and back it up in the recovery and try to restore. But I never put any encryption on my device let alone it doesn't even ask me for a password when I am on the recovery. Anyway, I solved it by just flashing the latest official TWRP on our device. And I'm glad that I am finally away from the buggy chinese twrp.
I was just worried if there was any dangers on flashing the official latest twrp because I am seeing a lot of people getting bricked. So much for the halfassed allowing us to unlock our bootloader in this device by leeco.
Anyway, I really appreciate all that detailed guide. I will keep them in reference in the future.
drckml said:
Thanks for the detailed response!
my issue was, I can go to recovery but it is not mounting my internal storage. It was showing as 0mb. I am aware that this is usually happens when you encrypt your device and back it up in the recovery and try to restore. But I never put any encryption on my device let alone it doesn't even ask me for a password when I am on the recovery. Anyway, I solved it by just flashing the latest official TWRP on our device. And I'm glad that I am finally away from the buggy chinese twrp.
I was just worried if there was any dangers on flashing the official latest twrp because I am seeing a lot of people getting bricked. So much for the halfassed allowing us to unlock our bootloader in this device by leeco.
Anyway, I really appreciate all that detailed guide. I will keep them in reference in the future.
Click to expand...
Click to collapse
That's great!
In the future
If you have an encryption issue again, and you have latest tarp and magisk.
Just format storage and reboot to recovery, then wipe and issue will be resolved.