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?
Friends, I am newbie in custom roms. Phronesis rom seems good and easy to install. Even being easy to install, I was unable to install Phronesis rom. The steps that I followed to install this rom are given below.
1) Downloaded Phronesis v6.2 rom from OP and copied it to SD Card.
2) Booted into TWRP recovery.
3) Selected "Wipe" option in the recovery menu.
4) Selected Advanced wipe.
5) From this menu I selected system, data, cache and delvit/art cache.
6) After selecting above options I swiped to wipe.
7) After this I went back to main recovery Menu.
8) From recovery menu I selected Install.
9) From here I chose Phronesis v6.2 rom from SD card storage.
10) Installation started and a bar started to load on the bottom of screen.
And after a few seconds (10 to 30 sec) my phone restated and stuck on note 3 logo.
At the end I didn't have any option but to re-flash stock firmware using odin.
It is the horror story of my note 3.
Please tell me where I have done wrong.
Read the FAQS and Q&A for the rom.
Especially the Q&A regarding TWRP
Did you go through Aroma installer ??
No sir, aroma installer did not start. My phone restarted spontaneously without going into aroma installer.
I have a similar Problem. I think this is caused by an incompatible (old) bootloader. I still use stock Android 4.4.2. When reading about how to install Phronesis I also stumble upon "update to 5.x first" to get a current bootloader.
Unluckily I'm not sure howto update the bootloader manually - but this could be the solution.
http://forum.xda-developers.com/galaxy-note-3/general/direct-download-bootloaders-modems-t3258803
Use TWRP 2.8.. latest version doesn't work. Check the MD5, is possible that the downloaded file is corrupted
You should really change the thread title to : Please spoon feed me, because i don't want to read at least the first thread page of the rom I'm trying to install !
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
B352 Boot_Insecure_B352_Fix-adb_dm-verity-v2.img
Download:
Download
Many thanks for created goes to Franzroy from Mate 8 Forum
Flash via Fastboot,boot into Twrp and flash Supersu 2.82
New Update to B350 Stock rooted
Downloads:
Download B350 Stock Rom
Download Twrp 3.1.0-3 from P9 Plus Eva
Download Boot_Insecure_B350_Fix-adb_dm-veritySpezial Thanks to franzroy from the Mate 8 Forumfor the Boot img
1,Wipe everything in Twrp,Format Data with "yes",in advanced wipe Dalvic,Cache,System,Data,Cust and internal Storage
2,install B350 Stock Rom in Twrp and Reboot
I add in the Rom Google Playstore,Calender and Contact Sync,Gmail and Youtube,Chrome and replace the PicoTTS with GoogleTTS (PicoTTS it does not work)
You can uninstall all extra Google Apps which I have added.
Rooted with Stock Boot img
I downloaded the update with Firmwarefinder,more times but it of 3 files only one functioned.
I have then put days-long and have managed to make from 2 scripts one and it is working.
You have a Full Rom with included Userdata.
New Root Procedure B332 works 100% and very easy
Downloads:
Download B332 Full
Boot_Insecure_B332_Fix-adb_dm-verity.img Spezial Thanks to franzroy from the Mate 8 Forum Without him it would not be possible!
3.1.0-0 Twrp
Superuser for Emui 5
Download all 4 Files (Full Rom B332,Boot_Insecure_B332_Fix-adb_dm-verity.img,Twrp and Supersu.)
Extract Full Rom B332 with Winzip or 7zip,Winrar....
Copy Full B332 Rom (Update.zip,update_data_full_all_cn.zip),Supersu on your SD Card.
1 Install Twrp via Fastboot or in Twrp via Image flash.
2 Install update_data_full_all_cn.zip (Don´t Reboot after install this)
3 Install update.zip and Reboot into System and make via Settings a Low Level Factory Reset (Factory Reset with internal Memory to mount Data in Twrp)
4 Install Twrp again via Fastboot
5 Flash in Twrp via image flash the Boot_Insecure_B332_Fix-adb_dm-verity.img (Or flash via ADB,both Variants works)( fastboot flash boot Boot_Insecure_B332_Fix-adb_dm-verity.img )
6 Flash Superuser for Emui 5
7 Reboot -Finish
Are you already on B332 with Twrp installed,flash via Fastboot or Twrp image flash the Boot_Insecure_B332_Fix-adb_dm-verity.img and then Superuser for Emui 5
I'm not sure if it works.
Supersu is not installed download from here and install
Download Supersu.apk
Here is Google Contact and Calender sync and the lastest Playstore.
Unpack the file and install as apk.
Download Google Pack
OLD Root Prozedure B320 Does not work 100%
Same Procedure,Flash in Twrp,i flash from B029 and works
The first Beta of Nougat for the Honor note 8.
The official version will be released next month in April
I have made some screenshots under Attachment
Emui 5.0 now has an appdrawer!(See the Pic´s in Attachment)
Attention
At the moment there is no way to go back to Emui 4.1
Requirements:
Unlocked Bootloader Here Thanks to jdantow for Manual
Installed B029 Stockrom
Installed old Twrp for Emui 4.1 Download
You Need:
Copy all the Things in your Extenal Memory/SD Card you need in Rooting Part
Decrypted Data Boot.img B320 Download Special Thanks to franzyroy for Creating the Decrypted Boot img
Twrp for Emui 5.0 Download
Here is a another Thread for Twrp,but this works not for me,i can´t Data not mount
Superuser for Emui 5.0 DownloadThanks to Chainfire for Supersu
Update.zip and update-data_full_all_cn.zip Here Thanks WhySoSeriousJoKer for Uploading
First:Install Full B320 Stockrom without Root
Are you on Android 6.0 Emui 4.1 B029 Stockrom
1.Boot into Twrp and Wipe Factory reset
2.Wipe --> Format data --> to write: yes - confirm
3.Install update_data_full_all_cn.zip - Don't reboot
3.Install update.zip
6.Reboot Wait 5 minutes (Possibly a factory reset If the device does not boot)
You are on B320 Android 7.0 with Emui 5.0 (Stock Recovery after this Procedure is installed)
Second:Root the Device
1.Stock Recovery is installed, Twrp must be installed again the new Version for Emui 5.0
2.Install the B320 Decryped Boot.img in Trwp ( or via Adb/Fastboot
3.After installed the Decryped Boot.img Boot into Twrp and Wipe --> Format data --> to write: yes - confirm,It takes very long.
4.Abort the Data Format,for this press the power button for 10 seconds until it restarts,and boot into eRecovery with Press and hold 3 Sec the Volume up.
5.In eRecovery select Format data partition.
6.After Format Data Shut Down.
7.Press First Volume up and then Power Button and hold both Buttons to Reboot into Twrp.
8.In Twrp Press Mount and see if data is mounted.Is Data Mounted is all ok.
9.Wipe/System,Data,Cache and Dalvik
10.Go back to install SuperSU-v2.79-201612051815-EMUI5.0.zip Don't reboot
11.Go Back to install and install update_data_full_all_cn.zip Don't reboot(You can extract the update_data_full_all_cn.zip and delete some China apps before they are installed)(Unpack-delete Apps/Repack with Winzip or 7 Zip)
12.Go back to install and install update.zip Don't reboot
13.Go back to install and install SuperSU-v2.79-201612051815-EMUI5.0.zip
14.Reboot the Phone it´s reboot´s Two times and it´s normal and after reboot go to Superuser App and open it,comes no error message fits everything.
After the Rooting Procedure is automatically the Stock Recovery installed!
You can reboot in Bootloader and install Twrp again and Data is Mounted.
This is almost the same procedure as the Mate 8 and I have also made it at the Mate 8 and it worked immediately
So much thanks to franzyroy
Sorry for my bad English and i hope you understand!
Mods:
Change the Icon Size:
Use Rootexplorer or Es File Manager and go to:
cust/all/cn/prop
Open the Local.prop with an Texteditor
Search the Line:
######2.BASEAPP TEAM BEGIN
under this Line write:
ro.config.app_big_icon_size=136 (or what you want the size of the icons,136 is very small,look the Pic in Attachment)
This must look like this now
######2.BASEAPP TEAM BEGIN
ro.config.app_big_icon_size=136
Save und look the right Permission torw-r--r--
and reboot
Remove in Music and Videoplayer the China Services:
same here,go in
cust/all/cn/prop
Open the Local.prop with an Texteditor
Search the Line:
######2.BASEAPP TEAM BEGIN
under this Line write:
cofig.onlinevideo.enabled=false
ro.cofig.onlinemusic.enabled=false
Save und look the right Permission torw-r--r--
and reboot
Now you have Video and Music Player without the China Online Service.
Look the Pic´s in Attachment
Or Download my local.prop with this 3 Mods ,unpack with win zip and copy the "local.prop" in cust/all/cn/prop with an File Explorer with root Support,overwrite your local.prop,Save und look the right Permission torw-r--r--
and reboot
Backup your local.prop on Micro SD Card before!
new thread old guy asking...
good idea you started new thread...
part 2
about 2.- if installing boot.img from twrp, which partition to use? bootloader? if installing from twrp I stay in twrp or must restart after install boot.ing... And 1 security question- will room boot after this?
3. and 4. you said format data takes too much time. You never suggest to wait it , but break and go in point 4.?
ivanox1972 said:
new thread old guy asking...
good idea you started new thread...
part 2
about 2.- if installing boot.img from twrp, which partition to use? bootloader? if installing from twrp I stay in twrp or must restart after install boot.ing... And 1 security question- will room boot after this?
3. and 4. you said format data takes too much time. You never suggest to wait it , but break and go in point 4.?
Click to expand...
Click to collapse
In Twrp flash Image there are only 2 options to choose from
Boot or Recovery
For Boot.img use:Boot
For Recovery Twrp or Stock Recovery use:Recovery
Yes wipe Data and after 10 sec wiping Press so long the Power Button to Reboot the Device,If you see the black background with oranges text,3 options are available.
You take Press for 3 sec Volume up to reboot in eRecovery.
In eRecovery is then Format Data Partition.Formate Data Partition and Shut Down the Phone
Reboot into Twrp go to Wipe,Wipe Data--Yes,now it works in Twrp
Go Back to Advanced Wipe and wipe Dalvik,Cache,Data and System.
Do not Reboot!
Flash supersu
Flash Update_data_all_cn.zip
Flash Update.zip
Flash Supersu again
Reboot-wait for 5 Min
Stuck on Huaweilogo Factory Reset and the Phone Booting.
Last sentence/ if final boot fail and stuck on logo, how to wipe?
I now check erecovery before start, 3 options there:
Install firmware and recovery
Shutdown
Reboot
How to wipe data from there for step 3 and 4?
Sent from my SM-T815 using XDA-Developers Legacy app
ivanox1972 said:
Last sentence/ if final boot fail and stuck on logo, how to wipe?
Sent from my SM-T815 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Step 14?
Press Power Button 10sec for reboot
During the reboot press volume up and Power Button and hold both Buttons,see you the black Background with organges text release the buttons
It´s boot to Stock recovery,Factory reset and wipe cache and reboot
the Phone boot into System
Ok, look please other part of question:
How to format data from erecovery, no this option
Sent from my SM-T815 using XDA-Developers Legacy app
I don't know if I understand correctly (I'm new to this stuff) but I got back to Emui 4.1.
I installed the Rom without root successfully but messed up the instructions to root and got stuck in some sort of bootloop.
Then Emui reinstalled a factory fresh B027 over wifi and upgraded to B029.
I think this happened with charge/data cable plugged into the PC and pressing the volume up button on reboot.
Apologies if that is not what you meant but it seems to be difficult to brick the phone
ivanox1972 said:
Ok, look please other part of question:
How to format data from erecovery, no this option
Sent from my SM-T815 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I say abort the Data Wipe in Twrp and boot into e Recovery,there is a Option to wipe Data Partition,this Option is only if abort data wipe in Twrp
tiggrr1 said:
I don't know if I understand correctly (I'm new to this stuff) but I got back to Emui 4.1.
I installed the Rom without root successfully but messed up the instructions to root and got stuck in some sort of bootloop.
Then Emui reinstalled a factory fresh B027 over wifi and upgraded to B029.
I think this happened with charge/data cable plugged into the PC and pressing the volume up button on reboot.
Apologies if that is not what you meant but it seems to be difficult to brick the phone
Click to expand...
Click to collapse
Always got back with flash update_data_all_cn and Update zip.
My HN8 works fine and i root successfully
Great, I don't know this, never break wipe before. Puzzle is almost settled. I will probably try afternoon.
Have you solved viber WhatsApp notification?
And most problem: brightness drop in browser?
Thanks x 10000000.
Sent from my EDI-AL10 using XDA-Developers Legacy app
@letschky
Have you solved viber WhatsApp notification?
And most problem: brightness drop in Browser and dialer?
I copy Whatsapp in System/App,give Permissions and no Problems.
Which Brightness Problem? I have not Problems with it.
Ok, for viber and WhatsApp same solution as on 4.1?
Try any browser in middle light conditions / system reduce brightness in browser and dialer more then any other app and more then is ok for use...
https://forum.xda-developers.com/showthread.php?t=3559949
On all huawei nougat same problem
I'm having problems copying Apps on System/App folder. When I try copying the APK file, it says there is not enough space. I even tried in TWRP and it is says it can't copy it. I even tried mounting the system folder. Any ideas?
Sent from my EDI-AL10 using Tapatalk
using, it is super fast but I have some problems:
-nova launcher unread notifications counter can not be switch on. It is switched on, but go off immediately
UPD.: solved by give nova and tesla unread every possible rights in phoneManager and apps..
-it seems to me that non huawei app (google, chrome, any...) have some delay on opening, like OS check them somehow?
- browser in middle light conditions / system reduce brightness in browser and dialer more then any other app and more then is ok for use...
https://forum.xda-developers.com/sho....php?t=3559949
If somebody not see this: on middle bright conditions open chrome, brightness drop. Tap navigation key recent apps, chrome is in foreground it is clear seen that brightnes rise. tap again chrome, brightness drop whet it on stays active... ugly. it was same in emui 4.1 but as solving by batery mode performance option use instead balanced
probably they have not made battery profiles for beta version and nothing can be done...
UPD.: solved by force stop, dissable boot, freeze Power Genius (com.Huawei.powergenie) in sd maid.
maybe imonitor (com.huawei.imonitor) is also battery app, if somebody knows??
What bugs that you faced after booting the Rom ? Is this version stable for daily use
And Thank you so much for posting this thread
@letschky WHAT is best procedure to roll back to b027?
I just got this phone about 8 days ago, and I have a few questions if anyone can answer, I already had the EMUI 5.0 installed on my phone (a reset of the phone triggered a download after signing up with the Huawei ID).
1) I noticed that after I installed the decrypted boot image some of the features disappeared, like the themes, and the changing of the pictures on the lock screen, and the icons seems to be all over the place.
2) I noticed some of the settings are missing, like before rooting and unlocking there was an option to save power by making the screen dark, now it seems that option is gone.
3) If after rooting could you re-lock the bootloader and still keep root?
Also lastly, does anyone here have the english version of HiVoice (HwVAssistant.apk) thats not deodexed? I wanted to try this out but the only version I see is the deodexed and I havent tried yet but I think it still wont work on a rooted phone since the rom isnt deodexed. The reason I am asking is my car is picking it up as Siri (I know its not) but if it works like siri it would be golden.
Welp I cant get my phone back, I was trying to get back to stock, and nothing is working stuck at the honor logo, even tried to go back to emui 5.0 following the directions here, but data keeps not staying mounted. And recovery over WLan wont work because it says failed to get package info. Anybody have any ideas?
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