Develop Bugs

[HELP ME]Xperia S and CYANOGENMOD 11

Hello there, sorry for the trouble but I need some help...
I have a Xperia S device bought here in Italy, I unlock it following a guide on this forum (through sony site), and wanted to install Cyanogemod 11 on my Xperia.
I'm blocked at this point, for you the info of my Xperia S:
Model: LT26i
Android Version: 4.1.2
Version: 8660-AAABQOLYM-314010-39
Kernel Version: 3.4.0+1.0.21100-313065-g1ccebb5-00193-gcbc50fc
N. Build: 6.2.B.1.96
What I have to do to continue? Could you tell me and step by step the things I have to do to install correctly the Cyanogenmod on my Xperia posting also the guide to follow?
I would put a recovery if is possible...
Thanks before, Hope in answer.

1.unlock bootloader
2.root it
3.install cwm or twrp
4.download the Rom u wqnt to install
5.and flash according to the instructions given in op.
Now u r good to go....
Sent from my LT26ii using xda premium

nisu4717 said:
1.unlock bootloader
2.root it
3.install cwm or twrp
4.download the Rom u wqnt to install
5.and flash according to the instructions given in op.
Now u r good to go....
Sent from my LT26ii using xda premium
Click to expand...
Click to collapse
I already unlocked the bootloader, but how I can do the root and install the cwm?
I have 6.2.B.1.96 build, and don't know which guide follow, could you give me link for 2 guides, 1 for root and 1 for cwm that are good for my terminal?
Even if I can put CM11 without root, so if is possible which guide i have to follow?
Sorry for disturb.

LukEel said:
I already unlocked the bootloader, but how I can do the root and install the cwm?
I have 6.2.B.1.96 build, and don't know which guide follow, could you give me link for 2 guides, 1 for root and 1 for cwm that are good for my terminal?
Even if I can put CM11 without root, so if is possible which guide i have to follow?
Sorry for disturb.
Click to expand...
Click to collapse
Root with this : [ROOT][S/SL] How-to for rooting newest firmware 6.2.B.1.96
CWM : [CWM-TWRP]Xperia S Dual Recovery for locked/unlocked bootloaders
Usually You need to root to install any custom ROM.

Mirhawk said:
Root with this : [ROOT][S/SL] How-to for rooting newest firmware 6.2.B.1.96
CWM : [CWM-TWRP]Xperia S Dual Recovery for locked/unlocked bootloaders
Usually You need to root to install any custom ROM.
Click to expand...
Click to collapse
Damn, I was doing the "rooting", following your guide (the first), I flashed the first file with flashtool and it worked fine, then when I went to move the folder "DooMLoRD_Easy-rooting-Toolkit_v18_perf-event-exploit" in C:\ and started the "runme_win" forgot to run it as an administrator and because of this or not the dos was stuck, I close the program and open it again as administrator because thought was this, but, when i run again the "runme_win" come out several errors then the procedure finish, the errors are about "Impossible found the path...", I checked even on the phone and i don't have nothing like SuperSu or other... possible solution?
I noticed that the phone number info Build is always 6.2.B.1.96, but if I flashed with "XperiaS_LT26i_6.2.B.0.211_KernelOnly", should change, right?
Help me
N.B:
The first time that i run "runme_win" without rights of administrator, the dos told me: "STARTING,WAITING FOR DEVICE,daemon not runnig, starting it now, daemon started successfully" then stops at this point and you can not do anything but close the program."
While the second time with rights of admministrator: "No such file or directory, is come out different times with several files"
EDIT: I solved, I tried again without administrator rights, I got this errors:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After this errors, everything is gone well, the SuperSU app is on my devices and work well, I continue to flash again the kernel as the guide says.

LukEel said:
After this errors, everything is gone well, the SuperSU app is on my devices and work well, I continue to flash again the kernel as the guide says.
Click to expand...
Click to collapse
Yeah, that run as administrator messes up a lot, You have to run it normally. So You got rooted and have a recovery, right?
About the version number, only the kernel number was changed, not Your entire firmware, so the firmware number doesn't change in "About Phone ".
Sent from my Xperia S using XDA Premium 4 mobile app

Mirhawk said:
Yeah, that run as administrator messes up a lot, You have to run it normally. So You got rooted and have a recovery, right?
About the version number, only the kernel number was changed, not Your entire firmware, so the firmware number doesn't change in "About Phone ".
Sent from my Xperia S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The recovery still not.
http://forum.xda-developers.com/showthread.php?t=2634382
First method, all good... but when boot the phone, and click volume + power it don't don't show nothing... just start normally.
Why ever?

LukEel said:
The recovery still not.
http://forum.xda-developers.com/showthread.php?t=2634382
First method, all good... but when boot the phone, and click volume + power it don't don't show nothing... just start normally.
Why ever?
Click to expand...
Click to collapse
Huh. Weird. You have to press volume up when You see the blue LED while booting. Try pressing it 2-3 times consecutively.
Don't know why I din't mention his earlier, but since You have an unlocked bootloader, You can flash a doomkernel. It has pre-installed recovery and all. DoomKernel

I solved. After the failed installation of CM11 my devices was blocked at LOGO Sony....
I got the firmware .96 and flashed it, after root with toolkit, and CWM the recovery on the phone, then I have installed CM11 and Gapps, all good.
The unique thing, is that, with the Installation of CM11 through CWM recovery, after the CM11 is started, I tried to go in recovery but instead of the CWM recovery there was the TWRP recovery... however all good, the recovery work well as the CWM.
Now im fiding the best rom for the Xperia S, do you have some advice?
I really don't know, and CM11 seems a bit hesitant in routine operations, maybe because is a Beta...
Regards!

LukEel said:
I solved. After the failed installation of CM11 my devices was blocked at LOGO Sony....
I got the firmware .96 and flashed it, after root with toolkit, and CWM the recovery on the phone, then I have installed CM11 and Gapps, all good.
The unique thing, is that, with the Installation of CM11 through CWM recovery, after the CM11 is started, I tried to go in recovery but instead of the CWM recovery there was the TWRP recovery... however all good, the recovery work well as the CWM.
Now im fiding the best rom for the Xperia S, do you have some advice?
I really don't know, and CM11 seems a bit hesitant in routine operations, maybe because is a Beta...
Regards!
Click to expand...
Click to collapse
Ah good that You got it solved. I would recommend Carbon ROM, but it has some issues going on currently. Try PAC, it is good one, and very stable for now.

LukEel said:
I solved. After the failed installation of CM11 my devices was blocked at LOGO Sony....
I got the firmware .96 and flashed it, after root with toolkit, and CWM the recovery on the phone, then I have installed CM11 and Gapps, all good.
The unique thing, is that, with the Installation of CM11 through CWM recovery, after the CM11 is started, I tried to go in recovery but instead of the CWM recovery there was the TWRP recovery... however all good, the recovery work well as the CWM.
Now im fiding the best rom for the Xperia S, do you have some advice?
I really don't know, and CM11 seems a bit hesitant in routine operations, maybe because is a Beta...
Regards!
Click to expand...
Click to collapse
hey use niaboc's rom existenz 2.0.5 and flash doomkernel last version everything works fine for me! if u are coming from cm do a fresh installation

[S3] device wont boot into recovery while flashing cf-autoroot via odin

hi there, i have a problem while trying too root my s3 using ct-autoroot.
after connecting and flashing it via odin everything goes smooth and fine but when it restarts my phone it won't boot into recovery it would only flash black screen with a blue font in the top saying "recovery booting..." then shut it self down. I watched some other video on youtube which their phone successfully boot into recovery->blackscreen->samsung->logo->recovery thats installing the new file from autoroot, but mine just doesnt work even if i clear the cache and tried to redo the steps, still gets "recovery booting" ->black screen->phone shutsdown
it was also stated on the chainfire autoroot website that
"For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually."
i have Samsung s3 (sgh-i747m)
carrier: bell
Android version: 4.1.2
P.s
I also tried installing root checker and tried to check my system but it says : "Sorry root access is not properly installed on this device"

Do you have any warranty left on your phone? Is your phone sim unlocked?
Since you're on 4.1.2, you can unlock your phone using the free method.

audit13 said:
Do you have any warranty left on your phone? Is your phone sim unlocked?
Since you're on 4.1.2, you can unlock your phone using the free method.
Click to expand...
Click to collapse
thank you for answering i really appreciate it btw my phone is already sim unlocked and its already a year or two since the warranty expired

Did you solve the problem?

audit13 said:
Did you solve the problem?
Click to expand...
Click to collapse
nope, problem is still happening what i mean is its already sim unlocked before i tried to root. it still shuts down completely when trying to boot into recovery mode when flashing cf-autoroot for sgh-i747m

The easiest way to solve the problem would be to flash back to stock ROM, flash Philz d2lte recovery, and flash supersu from recovery.

audit13 said:
The easiest way to solve the problem would be to flash back to stock ROM, flash Philz d2lte recovery, and flash supersu from recovery.
Click to expand...
Click to collapse
ok thanks for answering ill try it

audit13 said:
The easiest way to solve the problem would be to flash back to stock ROM, flash Philz d2lte recovery, and flash supersu from recovery.
Click to expand...
Click to collapse
one question sir audit. will it be safe to flash a stock rom? i mean what if it fails to boot into recovery again. will it bricked my phone if that happens?

You can flash a stock rom from sammobile.com as long as you don't downgrade the bootloader.

audit13 said:
You can flash a stock rom from sammobile.com as long as you don't downgrade the bootloader.
Click to expand...
Click to collapse
hi , i successfully flashed 4.3 stock rom (because i cant find a 4.1.2 stock rom) what i noticed is the app called knox. i heard that it sometimes block you from rooting your phone. but when i clicked on it ,it ask me if i want to install it which is approximately 119mb of data but i havent clicked on it yet. I also check if its in my device security administration but it is not currently checked. Is it still safe to root my s3?

yves010598 said:
hi , i successfully flashed 4.3 stock rom (because i cant find a 4.1.2 stock rom) what i noticed is the app called knox. i heard that it sometimes block you from rooting your phone. but when i clicked on it ,it ask me if i want to install it which is approximately 119mb of data but i havent clicked on it yet. I also check if its in my device security administration but it is not currently checked. Is it still safe to root my s3?
Click to expand...
Click to collapse
audit13 said:
You can flash a stock rom from sammobile.com as long as you don't downgrade the bootloader.
Click to expand...
Click to collapse
Nevermind i already did it. i successfully rooted my device thanks a lot for helping me i can only show my gratitude my pressing the "thanks" button i hope its enough to thank you

If you update to the latest kk, the easiest way to root would be to flash a custom recovery and flash supersu via recovery.

audit13 said:
You can flash a stock rom from sammobile.com as long as you don't downgrade the bootloader.
Click to expand...
Click to collapse
is it fine to flash d2lte even thou my phone is a canadian version (bell carrier)
here's a screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

yves010598 said:
is it fine to flash d2lte even thou my phone is a canadian version (bell carrier)
here's a screenshot
Click to expand...
Click to collapse
d2lte is the unified version. you should be a.o.k.
"all i can really do , is stay out of my own way and let the will of heaven be done"

audit13 said:
You can flash a stock rom from sammobile.com as long as you don't downgrade the bootloader.
Click to expand...
Click to collapse
mrrocketdog said:
d2lte is the unified version. you should be a.o.k.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
thank you mrrocketdog and mraudit13 i only got a few knowledge about android stuffs. I already pressed thanks for your replies thank you

If phone screen isnt working how to flash
audit13 said:
The easiest way to solve the problem would be to flash back to stock ROM, flash Philz d2lte recovery, and flash supersu from recovery.
Click to expand...
Click to collapse
HI there, same problem I am facing as well. How to flash the stock ROM and recovery if the screen is not working? ODIN is not recognizing the device. No SD card as well.
My Galaxy S3 is SIM locked and with Bell .. Android 4.4.2 How to go back to normal mode again ? Thx.
Removed battery for a min, changed the USB port on the computer and attempted the process for about 5 times- then Volume down + Power + centre home button- started ODIN- recovery image was there as well.- flashed- Back to normal.. Sigh !

If you can't see the screen, the easiest way to get to download mode would be to use a USB jig. I purchased a jig soon after getting my Samsung Captivate. It has been used by me and several frieds to get ourselves out of a jam.

Alternative flash method?

Is there any other way to flash the Zenfone 2 than through recovery?
I received a CN version with WW software. It wasn't possible to flash to the latest WW because got build.prop error (Sku is CN error).
So I succesfully flashed to latest CN version. But the CN version has no Play store.
But now I can't flash back to WW because it's on the CN version now.
I hope you're following what I'm saying.
Is there some alternative flashing method where you can force the flash? I tried changing build.prop to CN Sku, but of course this ruined the signing.
What a mess.

damian5000 said:
Is there any other way to flash the Zenfone 2 than through recovery?
I received a CN version with WW software. It wasn't possible to flash to the latest WW because got build.prop error (Sku is CN error).
So I succesfully flashed to latest CN version. But the CN version has no Play store.
But now I can't flash back to WW because it's on the CN version now.
I hope you're following what I'm saying.
Is there some alternative flashing method where you can force the flash? I tried changing build.prop to CN Sku, but of course this ruined the signing.
What a mess.
Click to expand...
Click to collapse
What version of ROM are you on now? post screenshot .

smartbuddy said:
What version of ROM are you on now? post screenshot .
Click to expand...
Click to collapse
Thanks for your help smartbuddy.
I'm now on this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When it originally came, it came with: LRX21V.WW-ASUS_Z00A-2.13.40.13_20150401_8390_user......... But wouldn't offer up any OTA and couldn't flash newest WW because of CN Sku build.prop error. So upgraded to latest CN, but now stuck without any Google apps and some apps spouting CN even when switched to English. Ugh.

damian5000 said:
Thanks for your help smartbuddy.
I'm now on this
When it originally came, it came with: LRX21V.WW-ASUS_Z00A-2.13.40.13_20150401_8390_user......... But wouldn't offer up any OTA and couldn't flash newest WW because of CN Sku build.prop error. So upgraded to latest CN, but now stuck without any Google apps and some apps spouting CN even when switched to English. Ugh.
Click to expand...
Click to collapse
1) Download recovery image file (https://app.box.com/s/ohk0aki3nfxjqyuygbl629612tfmi6d9)
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash recovery by using command : fastboot flash recovery recovery.img
4) reboot to fastboot again
5) launch recovery from fastboot
6) Flash the latest WW firmware same way u flashed latest CN firmware
7) wipe cache
8) reboot

smartbuddy said:
1) Download recovery image file (https://app.box.com/s/ohk0aki3nfxjqyuygbl629612tfmi6d9)
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash recovery by using command : fastboot flash recovery recovery.img
4) reboot to fastboot again
5) launch recovery from fastboot
6) Flash the latest WW firmware same way u flashed latest CN firmware
7) wipe cache
8) reboot
Click to expand...
Click to collapse
Okay. Thank you. This has gotten me one step further. I'm now getting this error:
Can't install this package (Wed Apr 15 00:42:20 CST 2015) oer newer build (Thu Apr 16 14:55:02 CST 2015).
E:Error in /sdcard/MOFD_SDUPDATE.ZIP
(Status 7)
This is the correct ROM, I've checked build.prop: ro.build.version.incremental=WW_Z00A-WW_2.14.40.19_20150415_9660_user_rel-user-20150415
Indeed the date is older than what's on there currently. Even though Asus site says this was released on 4.27.
Any way to get around this? Or need to wait for some newer ROM to be released?

damian5000 said:
Okay. Thank you. This has gotten me one step further. I'm now getting this error:
Can't install this package (Wed Apr 15 00:42:20 CST 2015) oer newer build (Thu Apr 16 14:55:02 CST 2015).
E:Error in /sdcard/MOFD_SDUPDATE.ZIP
(Status 7)
This is the correct ROM, I've checked build.prop: ro.build.version.incremental=WW_Z00A-WW_2.14.40.19_20150415_9660_user_rel-user-20150415
Indeed the date is older than what's on there currently. Even though Asus site says this was released on 4.27.
Any way to get around this? Or need to wait for some newer ROM to be released?
Click to expand...
Click to collapse
Not sure if this would surely work but try the latest zip OTA update for WW Rom (2.15.40.10) from this thread : http://forum.xda-developers.com/zenfone2/orig-development/ota-links-stock-rom-t3093999

smartbuddy said:
Not sure if this would surely work but try the latest zip OTA update for WW Rom (2.15.40.10) from this thread : http://forum.xda-developers.com/zenfone2/orig-development/ota-links-stock-rom-t3093999
Click to expand...
Click to collapse
Okay. Will try. I'm not optimistic though. I'm on a totally different ROM than what this package is for. This is updated the same way as a full ROM?
Any other ideas am appreciating them.
The thing that's screwing me is the kernel on CN ROM is from 16th April.
There's nothing like Odin or some such to flash via PC?

damian5000 said:
Okay. Will try. I'm not optimistic though. I'm on a totally different ROM than what this package is for. This is updated the same way as a full ROM?
Any other ideas am appreciating them.
The thing that's screwing me is the kernel on CN ROM is from 16th April.
There's nothing like Odin or some such to flash via PC?
Click to expand...
Click to collapse
Instead of flashing the Rom from SD Card , use PC / Laptop to flash the WW Rom and follow the steps mentioned for Method 1 from here:
http://www.asus-zenfone.com/2015/04/how-to-flash-asus-zenfone-2.html
Ignore previous post as its just OTA update not complete Rom, so wont work, you need to get WW Rom on ur phone first and then apply OTA.

smartbuddy said:
Instead of flashing the Rom from SD Card , use PC / Laptop to flash the WW Rom and follow the steps mentioned for Method 1 from here:
http://www.asus-zenfone.com/2015/04/how-to-flash-asus-zenfone-2.html
Ignore previous post as its just OTA update not complete Rom, so wont work, you need to get WW Rom on ur phone first and then apply OTA.
Click to expand...
Click to collapse
Got up to like 40%, then:
E: Failed to verify whole-file signature
E: Signature verification failed
Crap. Frustration beginning to kick in. Have lost 8 hours of my life already.

Okay. This time got through verification, but same error again regarding kernel date. Ugh. Guess will have to wait until Asus modifies the kernel? Or someone smarter than I creates a signed ROM with a newer kernel date.

damian5000 said:
Okay. This time got through verification, but same error again regarding kernel date. Ugh. Guess will have to wait until Asus modifies the kernel? Or someone smarter than I creates a signed ROM with a newer kernel date.
Click to expand...
Click to collapse
I can understand your frustration bro, try this last one :
Flash system.img directly like you flashed recovery.img :
1) Download system image file (http://www.mediafire.com/download/xfnbk12g2kdbxpb/Z00A_2.13.40.13_preroot_system.zip)
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash system by using command : fastboot flash system system.img
4) wipe cache
5) reboot
I hope this works... :good:

smartbuddy said:
I can understand your frustration bro, try this last one :
Flash system.img directly like you flashed recovery.img :
1) Download system image file (http://www.mediafire.com/download/xfnbk12g2kdbxpb/Z00A_2.13.40.13_preroot_system.zip)
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash system by using command : fastboot flash system system.img
4) wipe cache
5) reboot
I hope this works... :good:
Click to expand...
Click to collapse
Butter, homie.
All good with Play so far. Haven't tested the network. Guess this is a bit of a frankenstein ROM now? I see kernel still reading the same, can flash kernel over via fastboot as well?
I've had strange behavior since got the phone trying to get into fastboot. Tough to do from boot. So have had to mostly do it through adb reboot fastboot. Also, every time I go into recovery it tries to update automatically to MOFD_UPDATE.ZIP. Whether I have an SD card in or not, tries to do the update from this file. Not sure if this is normal behavior or not. What do you think? (there's no option to select Update from SD within menu). Annoying. Every time try to go into recovery. (has had this issue since before Fn with it).
Anyways, what's your PayPal, man? Will forward you a tenner.

damian5000 said:
Butter, homie.
All good with Play so far. Haven't tested the network. Guess this is a bit of a frankenstein ROM now? I see kernel still reading the same, can flash kernel over via fastboot as well?
I've had strange behavior since got the phone trying to get into fastboot. Tough to do from boot. So have had to mostly do it through adb reboot fastboot. Also, every time I go into recovery it tries to update automatically to MOFD_UPDATE.ZIP. Whether I have an SD card in or not, tries to do the update from this file. Not sure if this is normal behavior or not. What do you think? (there's no option to select Update from SD within menu). Annoying. Every time try to go into recovery. (has had this issue since before Fn with it).
Anyways, what's your PayPal, man? Will forward you a tenner.
Click to expand...
Click to collapse
Yes recovery is annoying for the phone. Glad that this worked. Now you can flash latest stock rom via adb, this will update everything, but u will loose Root.
Regarding Paypal, I am happy that I was able to help, Thanks.

smartbuddy said:
Yes recovery is annoying for the phone. Glad that this worked. Now you can flash latest stock rom via adb, this will update everything, but u will loose Root.
Regarding Paypal, I am happy that I was able to help, Thanks.
Click to expand...
Click to collapse
I noticed kernel still reading 16th, so I took a shot and flashed boot.img over from the 15th (latest full ROM from Asus).
I'm very curious if the adb flash update will go fully successfully, but I have a feeling it will. I think I'll stick with root for now though...I really need to change DPI on this. FHD on 5.5"@240 (looks thereabouts) is not going to cut it.
It looks like lots of updates coming out regularly. Guessing someone will put out a new rooted system.img fairly soon.
I insist on the tenner man. Please send me a PM. I have learned a lot through this.

damian5000 said:
I noticed kernel still reading 16th, so I took a shot and flashed boot.img over from the 15th (latest full ROM from Asus).
I'm very curious if the adb flash update will go fully successfully, but I have a feeling it will. I think I'll stick with root for now though...I really need to change DPI on this. FHD on 5.5"@240 (looks thereabouts) is not going to cut it.
It looks like lots of updates coming out regularly. Guessing someone will put out a new rooted system.img fairly soon.
I insist on the tenner man. Please send me a PM. I have learned a lot through this.
Click to expand...
Click to collapse
Follow this thread, OP has posted latest Rooted System.img, recovery etc :
http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
DO NOT UPDATE SuperSU and su binary
If you wish to then pls donate to charity bro, Thanks !

Great help Smartbuddy! Actually I'm hoping that similar steps would work on my Asus Memo Pad 7 ME572CL with JP sku, as I want to change it to WW sku and update to latest firmware. Do you happen to know where I can get the equivalent WW recovery and system img files for that device?

smartbuddy said:
1) Download recovery image file (https://app.box.com/s/ohk0aki3nfxjqyuygbl629612tfmi6d9)
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash recovery by using command : fastboot flash recovery recovery.img
4) reboot to fastboot again
5) launch recovery from fastboot
6) Flash the latest WW firmware same way u flashed latest CN firmware
7) wipe cache
8) reboot
Click to expand...
Click to collapse
Thank you Man! It solve my problem! I had "...cannot over new build .....
(Status 7)" this error while updating from 63 to 90 firmware. Find the solution for few hour through google but nothing found ,almost despair TT . Finally found this thread and saved my phone! Thank you so much! :good:
Btw, ASUS phone is so trouble to flash a rom ><

Guide to unlock bootloader for realme c1, realme 2

EDIT WE HAVE SUCCESSFULLY FLASHED GSI arm 64 ab custom roms ( need vbmeta.img from realme 3 pro ) WITH MINIMAL BUGS, INSTALLED MAGISK ETC.
<Mod edit>
Hii guys it is possible to unlock the bootloader for Realme c1 and Realme 2 post A.59 update.. Here is how
- First of all you need to download Adb and fastboot drivers you can find link on google.
- Then unlock developer options by tapping version in about phone 7 times.
- Go to developer option and turn on usb debugging and oem unlock
- Connect the phone to your pc via usb cable and install adb drivers.
- Go to the directory where you have downloaded adb and fastboot and press shift + right click and then click on open command window here
- In the command window enter the following command
adb reboot bootloader
- it will ask for permission in phone then just allow it.
- Your phone will restart in bootloader mode
- Next step is simple, keep the phone connected and enter the following command.
fastboot flashing unlock
- On the phone screen select i want to unlock bootloader with volume down button and press power button to confirm..
Warning : Phone will reboot and it will start wiping the data so backing up the data is recommended..
Note : if fastboot command is showing waiting for device then simply go to device manager and you will see "android" with little warning icon
right click on that android and click update drivers then search for drivers online after that computer will detect the device...
some screenshots :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That is all.

Realme C1: after entering adb reboot bootloader, it says no devices/emulators found
---------- Post added at 07:53 PM ---------- Previous post was at 07:18 PM ----------
Thank you. I have unlocked Realme C1 successfully. Could you guide me how to root it ?

thatha said:
Realme C1: after entering adb reboot bootloader, it says no devices/emulators found
---------- Post added at 07:53 PM ---------- Previous post was at 07:18 PM ----------
Thank you. I have unlocked Realme C1 successfully. Could you guide me how to root it ?
Click to expand...
Click to collapse
i have no idea how to root it as i dont have working twrp, if you know any developer maybe you can request him to start some development as bootloader is unlocked now...
i could root it using magisk without recovery but that requires latest boot image of A.60 update but on realme website it only have A.23 stock rom

By mistake I haved flashed wrong boot.img to my Realme C1. Now It does not boot into system, only boot to Fastboot mode. Could anyone please share me stock boot.img of this phone or guide me how to flash stock rom. Thank you very much.

thatha said:
By mistake I haved flashed wrong boot.img to my Realme C1. Now It does not boot into system, only boot to Fastboot mode. Could anyone please share me stock boot.img of this phone or guide me how to flash stock rom. Thank you very much.
Click to expand...
Click to collapse
lol why would you flash wrong boot image without knowledge.. now your phone is bricked now your only hope is to go to realme service center or wait for custom recovery like twrp etc which may take a month or more or wait for realme to release latest stock firmware on their site..
On a side note you can try booting twrp recovery of some other phone like redmi 5 etc with the command
fastboot boot twrp.img
im noob so dont know if that will work or not but you can try

gau20 said:
lol why would you flash wrong boot image without knowledge.. now your phone is bricked now your only hope is to go to realme service center or wait for custom recovery like twrp etc which may take a month or more or wait for realme to release latest stock firmware on their site..
On a side note you can try booting twrp recovery of some other phone like redmi 5 etc with the command
fastboot boot twrp.img
im noob so dont know if that will work or not but you can try
Click to expand...
Click to collapse
After flashing fail, I check and discover that boot.img is for Realme 1, not Realme C1.
I think flash twrp recovery can't solve the problem because twrp is a recovery image, not boot image.
By the way, do you know how to extract boot.img from stock rom ? And how to flash stock rom ? I have downloaded some stock roms but when I open MSM download tool, it ask for user and password

thatha said:
After flashing fail, I check and discover that boot.img is for Realme 1, not Realme C1.
I think flash twrp recovery can't solve the problem because twrp is a recovery image, not boot image.
By the way, do you know how to extract boot.img from stock rom ? And how to flash stock rom ? I have downloaded some stock roms but when I open MSM download tool, it ask for user and password
Click to expand...
Click to collapse
dude there is no way to get stock boot image as of now since realme hasnt released latest stock firmware on their site.. the boot image that you will get will be an old one and it will not boot your phone....
what i am saying is try to boot a twrp recovery from other phone by using this command " fastboot boot twrp.img " then you can flash old stock rom through twrp and boot your device.. there is no boot image now that can boot your phone unfortunately.. the above mentioned way is the only way as of now or you can go to their service center..

gau20 said:
dude there is no way to get stock boot image as of now since realme hasnt released latest stock firmware on their site.. the boot image that you will get will be an old one and it will not boot your phone....
what i am saying is try to boot a twrp recovery from other phone by using this command " fastboot boot twrp.img " then you can flash old stock rom through twrp and boot your device.. there is no boot image now that can boot your phone unfortunately.. the above mentioned way is the only way as of now or you can go to their service center..
Click to expand...
Click to collapse
Thank you for the info. I am waiting for good news from you

thatha said:
Thank you for the info. I am waiting for good news from you
Click to expand...
Click to collapse
Hi, can you post the pic of bootloader as I have rooted many devices but not this one, and by the way you can flash the stock firmware to repair your device.

riyan65 said:
Hi, can you post the pic of bootloader as I have rooted many devices but not this one, and by the way you can flash the stock firmware to repair your device.
Click to expand...
Click to collapse
Attached image is my Realme C1 fastboot mode.
Could you guide me how to flash stock rom ? I have downloaded some stock roms but when I open MSM download tool, it ask for user and password

thatha said:
Attached image is my Realme C1 fastboot mode.
Could you guide me how to flash stock rom ? I have downloaded some stock roms but when I open MSM download tool, it ask for user and password
Click to expand...
Click to collapse
Can you post the firmware pic of firmware files??? As it will help to know which command is needed.

riyan65 said:
you can flash the stock firmware to repair your device.
Click to expand...
Click to collapse
Please help me. I try to flash stock firmware but msm download tool can not start, it ask for username and password to log in

riyan65 said:
Can you post the firmware pic of firmware files??? As it will help to know which command is needed.
Click to expand...
Click to collapse
picture of firmware file

thatha said:
picture of firmware file
Click to expand...
Click to collapse
Did you try crack to app, as it has suggested

No I can't crack

thatha said:
No I can't crack
Click to expand...
Click to collapse
were you successful in flashing stock rom??
if you can go to realme service center then they will fix it also can you try to flash gsi rom

gau20 said:
were you successful in flashing stock rom??
if you can go to realme service center then they will fix it also can you try to flash gsi rom
Click to expand...
Click to collapse
No, I can't open msmdownload tool

thatha said:
No, I can't open msmdownload tool
Click to expand...
Click to collapse
https://romprovider.com/2019/03/rmx1811-firmware-qfil/
you can try from here this is qfil flashable package..

gau20 said:
https://romprovider.com/2019/03/rmx1811-firmware-qfil/
you can try from here this is qfil flashable package..
Click to expand...
Click to collapse
Sahara fail

thatha said:
Sahara fail
Click to expand...
Click to collapse
EDIT : YOU HAVE TO HOLD JUST VOLUME UP TO BRING DEVICE TO DOWNLOAD MODE
did you start your phone in download mode and not fastboot mode?? by powering off your phone and then pressing both volume up and down key and connecting it to pc
also put rom files in c drive and remove any spaces in the directory name like C:\qfil files\ should be C:\qfil_files\ without space
also try with older version of qfil https://drive.google.com/file/d/0B3fyEuz1cnKpeDYtYnU0RXVqbEU/view
also try with Ultimate multi tool https://drive.google.com/drive/folders/1myq1coE1HyPn0QiVk4pY_Ym5Pw55RpeH

How To Guide Delete thread

Hello everyone.
Today i will be guiding you all for rooting Red Magic 6/Pro with bootloader locked as well as FP working.
Download the attached file.
extract on pc.
Now first things first enable developer options and Allow oem unlock.
Now once thats done Create a Magisk patched boot.img for your specific Fw. You can see this thread for that https://forum.xda-developers.com/t/...-the-red-magic-6-and-red-magic-6-pro.4266551/
now once we have magisk patch boot img copy it to pc and now reboot to bootloader/fastboot we can do that by vol down and power or by adb reboot bootloader
now execute step 1 in zip file you downloaded and unlock bootloader now the device will wipe and start up.
No need to setup just skip it.Now again reboot to bootloader and this time flash magisk patched boot image using.
fastboot flash boot magisk.img
now once thats done dont reboot now execute step3 and step 4 and select bootloader lock now the device will wipe and you will be rooted as well as Fp will be working.
This method has been tested by 4 devices on 3.12 and 4.12 and all worked successfully.Once again flash at your own risk and i am not responsible for any loss.
MOD EDIT: Telegram link removed, only development thread is allowed to have one telegram group for support.
Thanks Do let me know if you face any issue or problem
Moderator Edit: Attachment removed because it contains virus as reported by users and my own Firefox browser. Please scan your computer and proceed with cautions.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

great work. really appreciated. will test it soon enough i have so much data need to back up first

can i do this on cn rom? and btw where is this "steps" coming from? sorry just a newbie

kittyshik said:
can i do this on cn rom? and btw where is this "steps" coming from? sorry just a newbie
Click to expand...
Click to collapse
Yes. In summary, the steps are as follows:
1: unlock bootloader
2: flash magisk patched/rooted boot.img
3: flash unprotected vbmeta (in the zip)
4: relock bootloader
@alibroproshrow I would recommend adjusting the process:
1: flashing the vbmeta; the command should read:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta
2: erase userdata/cache via fastboot -w
3: then relock the BL

kittyshik said:
can i do this on cn rom? and btw where is this "steps" coming from? sorry just a newbie
Click to expand...
Click to collapse
yes it works for all

adwinp said:
Yes. In summary, the steps are as follows:
1: unlock bootloader
2: flash magisk patched/rooted boot.img
3: flash unprotected vbmeta (in the zip)
4: relock bootloader
@alibroproshrow I would recommend adjusting the process:
1: flashing the vbmeta; the command should read:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta
2: erase userdata/cache via fastboot -w
3: then relock the BL
Click to expand...
Click to collapse
No need to disable VBMETA
2: (erase userdata/cache via fastboot -w) That will brick the device if we do from fastboot after flash vbmeta and locking the bootloader the device automatically restarts and resets so no need.
3(flash unprotected vbmeta (in the zip))- Its a special Vbmeta and works on all Don't try stock fw vbmeta ,Only use the on in the zip file.

kittyshik said:
can i do this on cn rom? and btw where is this "steps" coming from? sorry just a newbie
Click to expand...
Click to collapse
There are step.bat in zip file You just need a Magisk patched boot.img for your ROM

Hey, my RM6 is on 4.15 somehow. May I ask if there's a way to get boot image for that version or if the boot.img from 4.12 is still compatible?
Thanks.

do i run th
alibroproshrow said:
There are step.bat in zip file You just need a Magisk patched boot.img for your ROM
Click to expand...
Click to collapse
that bat file is just instruction? or do i run that?

do i run th
alibroproshrow said:
There are step.bat in zip file You just need a Magisk patched boot.img for your ROM
Click to expand...
Click to collapse
oooh i get it noooow hehe xD thnx bruuuh

kittyshik said:
do i run th
that bat file is just instruction? or do i run that?
Click to expand...
Click to collapse
run bat

FoodBar said:
Hey, my RM6 is on 4.15 somehow. May I ask if there's a way to get boot image for that version or if the boot.img from 4.12 is still compatible?
Thanks.
Click to expand...
Click to collapse
downgrade to 4.12

alibroproshrow said:
downgrade to 4.12
Click to expand...
Click to collapse
Thanks, worked beautifully.
May I ask if the same vbmeta will work for versions going forward or is it specific to the 3|4.12 version?

FoodBar said:
Thanks, worked beautifully.
May I ask if the same vbmeta will work for versions going forward or is it specific to the 3|4.12 version?
Click to expand...
Click to collapse
yes it works on all versions

Can anyone tell me if bootloader locked after that i can receive OTA Updates?

Kirolod said:
Can anyone tell me if bootloader locked after that i can receive OTA Updates?
Click to expand...
Click to collapse
yes

alibroproshrow said:
run bat
Click to expand...
Click to collapse
when receiving ota updates and updating ..is root still intact? imean does it go off then i have to do it again?

im getting that this is a virus and I cannot download

kittyshik said:
when receiving ota updates and updating ..is root still intact? imean does it go off then i have to do it again?
Click to expand...
Click to collapse
nope

sata700 said:
im getting that this is a virus and I cannot download
Click to expand...
Click to collapse
turn off antivirus and if using chrome Ctrl+J and select keep file