Hello everybody, hope u doing fine.
i was looking to root my pixel, so i installed kingroot and it rooted it just fine, then i wanted a root manager so i went to play store installed supersu (i guess that was the cause, i shouldn't have done that),then i opened it, it asked to download binaries(or install i'm not quite sure...), anyway this went fine too, then it sayed, everything gone right, restart your device, i clicked in reboot, it restarts with google logo and animations, but it bassicaly wont boot it is just stuck at the dots animation.
the problem is that i left oem bootloader locked, so now i can't do anything via fastboot adb... when i do: fastboot oem unlock , it says: failed (remote: oem unlock is not allowed)
i searched a bit more and found that we can unbrick qualcomm powered devices with qfil flashing tool, but requires a firmware wich is in .mbn format, wich i don't find on the internet (at least for the pixel), maybe there's a custom rom in mbn format...
i'm on android 7.1.2, stock rom, unlocked version.
please tell me if there's a way to fix that,
thank you in advance ? !
luigigigi said:
Hello everybody, hope u doing fine.
i was looking to root my pixel, so i installed kingroot and it rooted it just fine, then i wanted a root manager so i went to play store installed supersu (i guess that was the cause, i shouldn't have done that),then i opened it, it asked to download binaries(or install i'm not quite sure...), anyway this went fine too, then it sayed, everything gone right, restart your device, i clicked in reboot, it restarts with google logo and animations, but it bassicaly wont boot it is just stuck at the dots animation.
the problem is that i left oem bootloader locked, so now i can't do anything via fastboot adb... when i do: fastboot oem unlock , it says: failed (remote: oem unlock is not allowed)
i searched a bit more and found that we can unbrick qualcomm powered devices with qfil flashing tool, but requires a firmware wich is in .mbn format, wich i don't find on the internet (at least for the pixel), maybe there's a custom rom in mbn format...
i'm on android 7.1.2, stock rom, unlocked version.
please tell me if there's a way to fix that,
thank you in advance ? !
Click to expand...
Click to collapse
Did you try turning the phone off and then using the power-on + volume down key to get to the bootloader menu? from there press the volume up key until you get to recovery and the press the power button. In recovery do a factory reset. That should take care of stuff. In future, don't use kingroot as it's a malware ridden app (that is if you care about your personal data). If you need root then use Magisk instead. Gives you root and also a root manager. If you are planning to tamper with root then make sure to have your bootloader unlocked. Let me know if factory reset worked.
yes i tried to factory reset it from recovery mode ( i did that twice ) and that didn't help.
luigigigi said:
yes i tried to factory reset it from recovery mode ( i did that twice ) and that didn't help.
Click to expand...
Click to collapse
I have one more idea you could try. Download latest OTA update from here: https://developers.google.com/android/ota
go into recovery and follow the instructions given on the link I just gave you and apply the update using adb sideload in recovery. (You have to manually get into recovery as you did before but follow the instructions from the point where you're inside the recovery.) This should work. Seems that kingroot/supersu corrupted your system somehow. Let me know if it worked.
i already came across that site because i was on android p, i didn't like it so i went back to nougat...anyway to say that i have the nougat image .zip , so do i have to download the latest firmware ?
ok ok, that's not the same...SORRY ?? !!
luigigigi said:
ok ok, that's not the same...SORRY ?? !!
Click to expand...
Click to collapse
yeah, it's not the same and you'll find the 8.1.0 update there and the updates from the past. Give it a go and tell me the results when you're done
i tried that, everything went as intended, when i power it up there's animations of 8.1 but still wont boot.
i tried to wipe data and boot again, nothing.
is there a way to flash stock rom with adb (just like we did with that update) ?
now, the phone just booted up and i'm on the set up screen, BUT it showed me a pixel 2 , and theres a lock at the top left corner and it asked for a pattern (cause i did a wipe)... it's like another phone stuck in mine ?!
---------- Post added at 04:28 PM ---------- Previous post was at 04:26 PM ----------
[/COLOR]
luigigigi said:
now, the phone just booted up and i'm on the set up screen, BUT it showed me a pixel 2 , and theres a lock at the top left corner and it asked for a pattern (cause i did a wipe)... it's like another phone stuck in mine ?!
Click to expand...
Click to collapse
It's the newer setup screen. Have you managed to boot into system. Is everything working?
Arju said:
---------- Post added at 04:28 PM ---------- Previous post was at 04:26 PM ----------
[/COLOR]
It's the newer setup screen. Have you managed to boot into system. Is everything working?
Click to expand...
Click to collapse
no since i did a wipe ( i guess i shouldn't have done that) , now when it boots it is locked, it is asking for a pattern, wjch i don't know because i didn't set a pettern previously.
i guess i'm stuck here for ever ? ??
is there a way to flash the stock firmware via stock recovery or external flashing tools on pc, if yes please explain how !
((((Update))))
I didn't notice that there was a connect to Google option, so I finally set up the phone with my Google account and I'm back in.
I'm very thankful to you man you saved my phone, thank you a lot.
(Are you from India ? ? I love a lot India it's a beautiful place to visit and I really hope I could travel there once in my life, greatings from Algeria ?? )
luigigigi said:
(Are you from India ? ? I love a lot India it's a beautiful place to visit and I really hope I could travel there once in my life, greatings from Algeria ?? )
Click to expand...
Click to collapse
I'm glad it worked itself out.
I'm from Norway. Married a swede so living in Sweden now. My parents are from Sri Lanka (the island below India) but moved to Norway before I was born. I've been to Sri Lanka once. Would like to travel to India sometime too :silly:
Algeria seems nice. Must be hot there. I've never been to Africa. Would like to travel there too some day
Yes totally, Algeria is really safe and people here won't bother you (like if you're wondering how u would be seen or received as a foreigner) there's foreigner all year round but especially in summer time, just have something planned in advance because it's Algeria not USA or another well developed country ? but still there's a lot to see here, definitely worth the visit.
When it comes to whether, well it's a Mediterranean weather so expect nice warm days, that being said, there's some time when it goes rainy with thunders and cold, for example now it is very pleasant outside, but yesterday the weather gone crazy... I guess that's because of the global warming.
luigigigi said:
is there a way to flash the stock firmware via stock recovery or external flashing tools on pc, if yes please explain how !
Click to expand...
Click to collapse
1) Install the Google Android driver if your Pixel isn't already recognized by your computer when booted to fastboot mode.
https://developer.android.com/studio....html#download
2) Download the factory system image for Pixel to C:/Google
https://developers.google.com/android/images
3) Unzip the system image folder into same folder, same with adb/fastboot tools in C:/Google
4) Run these commands in cmd prompt as administrator while Pixel is in bootloader mode
adb reboot-bootloader
fastboot flash bootloader bootloader-sailfish-*.img
fastboot reboot-bootloader
fastboot flash radio radio-sailfish-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
hope this helps
MpandAUS said:
1) Install the Google Android driver if your Pixel isn't already recognized by your computer when booted to fastboot mode.
https://developer.android.com/studio....html#download
2) Download the factory system image for Pixel to C:/Google
https://developers.google.com/android/images
3) Unzip the system image folder into same folder, same with adb/fastboot tools in C:/Google
4) Run these commands in cmd prompt as administrator while Pixel is in bootloader mode
adb reboot-bootloader
fastboot flash bootloader bootloader-sailfish-*.img
fastboot reboot-bootloader
fastboot flash radio radio-sailfish-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
hope this helps
Click to expand...
Click to collapse
I'm sure this gonna help me in the future, as i'm planing to try some custom Rom's and i'm probably gonna brick it again so ? ... Thanks you ? !
Related
My OPO is 100% stock currently running the second latest OTA update(coz I'd received a notification saying theres new update today but i haven't updated)
It was working perfectly fine until just now when I withdraw it from my pocket it shows the 1+ Powered by android loading screen.
I re-booted and it stuck at the same screen. I then boot into recovery and factory reset, wipe data wipe cache and boot and its still stucking at the same loading screen.
P/S : I was on wifi for a while in the cafe maybe it had downloaded the new OTA and maybe when the screen rubs against my pants in my pocket idk how it unlocks itself and it update itself with the downloaded(maybe) software update and eventually it dies. This might be one of the possibilities because if otherwise, it just dies itself without reason lel.
I've researched abit and someone suggested me to flash a stock rom using fastboot mode and PC adb command prompt which idk wtf is that lel. But in order to use that u need to unlock bootloader right, being 100% stock my bootloader is probably locked right?
omfg please guide me through this i need to solve this asap i dont have a backup phone. :silly::silly::silly::silly::silly::silly:
kingdew11 said:
My OPO is 100% stock currently running the second latest OTA update(coz I'd received a notification saying theres new update today but i haven't updated)
It was working perfectly fine until just now when I withdraw it from my pocket it shows the 1 Powered by android loading screen.
I re-booted and it stuck at the same screen. I then boot into recovery and factory reset, wipe data wipe cache and boot and its still stucking at the same loading screen.
P/S : I was on wifi for a while in the cafe maybe it had downloaded the new OTA and maybe when the screen rubs against my pants in my pocket idk how it unlocks itself and it update itself with the downloaded(maybe) software update and eventually it dies. This might be one of the possibilities because if otherwise, it just dies itself without reason lel.
I've researched abit and someone suggested me to flash a stock rom using fastboot mode and PC adb command prompt which idk wtf is that lel. But in order to use that u need to unlock bootloader right, being 100% stock my bootloader is probably locked right?
omfg please guide me through this i need to solve this asap i dont have a backup phone. :silly::silly::silly::silly::silly::silly:
Click to expand...
Click to collapse
Follow this
http://forum.xda-developers.com/oneplus-one/help/solved-how-to-recover-oneplus-soft-t2864800
OR
Agai u can manually download any cm firmware
Then go to recovery
Factory reset
And flash desired firmware
FOLLOW this ( this is cm12 os)
http://webtrickz.com/guide-to-update-oneplus-one-to-cm12-lollipop-os/
If u don't like lollipop u can flash cm11s
FOLLOW this
http://www.technobuzz.net/update-oneplus-one-cm-11s-44s-resolve-several-bug-fixes/
note: u can find most guides on Google just search with keywords of your problems
Second mentioned flashing methods are most easiest prrocess
Factory reset and flash u r zip file
Problem solved. Detailed solutions for noobs like me!
OKAY here is what I DID. it may not work for u, but it worked for me. so if ur gonna follow these steps do it at ur own risk. and please dont expect me to helpp u to counter any special circumstances i.e. any condition not stated here coz im a perfect noob too, lel.
FYI this is called flashing roms in fastboot mode. And i had successfully flashed my OPO back into CM12.
STEPS :
Using a windows PC:
1) Download the UNIVERSAL ABD driver for Windows and freaking INSTALL IT.
2) Download the OnePlus One CM12 factory image “cm-12.0-YNG1TAS0YL-bacon-signed-fastboot.zip” (fastboot flashable package).
3) Download the flashing tools. ( it contains 4 things: adb.exe AdbWinApi.dll AdbUsbWinApi.dll and fastboot.exe)
the download links are available from this link:
ok im not allowed to attach links but u can search for it " webtrickz[dot]com how to flash cm12 factory image fastboot mode"
however, the steps given in the above link are crappy as well so follow mine =P just do the downloadings only from there.
4) Extract the 4 things from the flashing tools zip file into a folder, name it whatever****ing folder u want. we call it folder X.
5) and then extract all the things in the CM12 rom zip file into folder X.
6) Boot ur phone into fastboot mode simply by pressing and holding down the power button and the volume up button simultanoesly until u see "fastboot mode" with an Android face appears.
7) Connect ur phone to your PC with a USB cable. Now ur phone should be connected to the pc in fastboot mode.
8) open up folder X. then right click in folder X while holding down the Shift button, and click on "Open command window here"
p/s : this, I think, is like a special way to open up a cmd prompt used specifically for abd/fastboot. U can also actually open up cmd prompt normally but in order to do that you need to install idk some **** so that ur NORMAL cmd prompt will recognise abd or whatever **** it is. however, if u do that, u do not need to extract the CM12 rom files into folder X as the NORMAL cmd prompt will have the ability to, sorta like detect the CM12 ****s. anyways, forget it, just ****ing use the special way i.e. go to folder X , shift + right click to open up the SPECIAL cmd prompt)
9) a command prompt(cmd) should appear, Now check if u are connected by keying in "fastboot devices" in the cmd. Then the serial number of ur phone should turn up, and not " waiting for device" "devices not found" or any messages of that sort.
If the latter appears, idk how to help u sort that out urself lel.
10) Now u have to unlock the OEM in order for this flashing process to work. idk whats unlocking oem but just unlock it FFS. To do this, simply key in "fastbook oem unlock"
11) I think that under normal circumstances, a pop-up will appear in ur phone to let u choose if u really wanna unlock this oem thingy. BUT for me, my phone just rebooted back into the ****ing 1+ Powered by android screen idk why, but its alright i was on the right track as my oem has been unlocked. Then i powered off my phone and booted in back into fastboot mode once again. (FYI whenever I have to boot my phone to fastboot mode I disconnect the usb cable idk if this is necessary but thats what i DID)
12) go back to the CMD just now, and freaking paste the commands listed below into the CMD.
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
13) Wait for several minutes, and when everything's done, the commands will stop at the last command which is "fastboot reboot"
Press Enter! and ur phone will reboot normally! =)
walpanmad said:
Follow this
http://forum.xda-developers.com/oneplus-one/help/solved-how-to-recover-oneplus-soft-t2864800
OR
Agai u can manually download any cm firmware
Then go to recovery
Factory reset
And flash desired firmware
FOLLOW this ( this is cm12 os)
http://webtrickz.com/guide-to-update-oneplus-one-to-cm12-lollipop-os/
If u don't like lollipop u can flash cm11s
FOLLOW this
http://www.technobuzz.net/update-oneplus-one-cm-11s-44s-resolve-several-bug-fixes/
note: u can find most guides on Google just search with keywords of your problems
Second mentioned flashing methods are most easiest prrocess
Factory reset and flash u r zip file
Click to expand...
Click to collapse
I can't flash it with recovery, as i cant 'insert' any ROM into my internal memory, as i cannot access my Internal memory, coz the phone wont boot?
However thank you so much! problem solved =)
kingdew11 said:
I can't flash it with recovery, as i cant 'insert' any ROM into my internal memory, as i cannot access my Internal memory, coz the phone wont boot?
However thank you so much! problem solved =)
Click to expand...
Click to collapse
Phone wont boot means?
If u are able to get in to recovery then its always possible to flash any official firmware without root with factory reset its easiest process to solve soft bricked device
First method mentioned is the same process u had done
(fastboot recover) but its automated process with OPO tollbox
Again fastboot method is usefull if u already enabled usb debugging in developer option before u went in to bootloop
I think u have previously enabled usb debugging
So it is also a method to recover u r problem
Any way its great news u got it worked
Hello Guys,
Please help me in the following case.
I have a Mate 7 TL-10. Originally, it was from China, it's system was Chinese.
Today, I rooted, I changed the location from CN to EU (I am from Hungary). Everything was okay, I wanted to flash a new (European) ROM, but before it, I wanted to wipe. Oh, no! Here, I was stupid. I wiped everything by that recovery, what the SRK Tool installs.
I lost everything, it wrote me, that no OS. I cannot enter to the recovery, it stucked at the Huawei logo. I even cannot switch the phone off, it only restarts!
Can you please help me to solve this problem and survive my phone?
Thank you for all in advance.
montisHU said:
Hello Guys,
Please help me in the following case.
I have a Mate 7 TL-10. Originally, it was from China, it's system was Chinese.
Today, I rooted, I changed the location from CN to EU (I am from Hungary). Everything was okay, I wanted to flash a new (European) ROM, but before it, I wanted to wipe. Oh, no! Here, I was stupid. I wiped everything by that recovery, what the SRK Tool installs.
I lost everything, it wrote me, that no OS. I cannot enter to the recovery, it stucked at the Huawei logo. I even cannot switch the phone off, it only restarts!
Can you please help me to solve this problem and survive my phone?
Thank you for all in advance.
Click to expand...
Click to collapse
Don't worry tell me what firmware you have is your bootloader unlocked or not it'll be fine don't worry...
fazi2015 said:
Don't worry tell me what firmware you have is your bootloader unlocked or not it'll be fine don't worry...
Click to expand...
Click to collapse
Hello!
Than kyou very much for your help. Yesterday night, I could survive the phone, this is what I did:
VOL- and POWER: fastboot mode
In fastboot mode, I connected to the PC and (beofr it, I downloaded an update.zip and extracted:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
Now, it is working (seems to be) But what should I do with the other .img files from the update.zip?
Do I have to do any other steps? I think yes, 'cause if I check the Vendor info in th*#*#2846579#*#* menu, there is no country code in my phone
Can you help me, what should I do?
Thank you for your help again.
montisHU said:
Hello!
Than kyou very much for your help. Yesterday night, I could survive the phone, this is what I did:
VOL- and POWER: fastboot mode
In fastboot mode, I connected to the PC and (beofr it, I downloaded an update.zip and extracted:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
Now, it is working (seems to be) But what should I do with the other .img files from the update.zip?
Do I have to do any other steps? I think yes, 'cause if I check the Vendor info in th*#*#2846579#*#* menu, there is no country code in my phone
Can you help me, what should I do?
Thank you for your help again.
Click to expand...
Click to collapse
You can download the mobopx app by chudy on the first post of this page:
https://forum.xda-developers.com/mate-7/general/huawei-mt7-l09-l10-stock-firmware-ota-t3275784
This app lets you change the country/vendor information on your phone, amongst other things
montisHU said:
Hello!
Than kyou very much for your help. Yesterday night, I could survive the phone, this is what I did:
VOL- and POWER: fastboot mode
In fastboot mode, I connected to the PC and (beofr it, I downloaded an update.zip and extracted:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
Now, it is working (seems to be) But what should I do with the other .img files from the update.zip?
Do I have to do any other steps? I think yes, 'cause if I check the Vendor info in th*#*#2846579#*#* menu, there is no country code in my phone
Can you help me, what should I do?
Thank you for your help again.
Click to expand...
Click to collapse
First off all you should flash your regional firmware(original) then if you want to change region changing region is not big deal download the official one and flash by putting update.app into dload folder in sd card and flash by force update and if you are able to flash recovery then flash twrp recovery and flash custom rom like @chudy rom & @Ale rom if you stay in official states then flash chudy rom much likely to stock and if you like custom rom then flash Ale rom which I use and many other.
Flash twrp recovery and make a full backup then wipe all without sd card and then flash the rom zip file after that wipe both cache and reboot first time it'll take some time but don't worry keep it booting you all done..
Further help needed please ask.:good:
montisHU said:
Hello!
Than kyou very much for your help. Yesterday night, I could survive the phone, this is what I did:
VOL- and POWER: fastboot mode
In fastboot mode, I connected to the PC and (beofr it, I downloaded an update.zip and extracted:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
Now, it is working (seems to be) But what should I do with the other .img files from the update.zip?
Do I have to do any other steps? I think yes, 'cause if I check the Vendor info in th*#*#2846579#*#* menu, there is no country code in my phone
Can you help me, what should I do?
Thank you for your help again.
Click to expand...
Click to collapse
same probleme here can you help me?
SOLVED!......
So hello guys, I am 17 year old, amateur in this mobile topic . My mobile is honor 8 with android 7.0
I unlocked my boot loader and then I tried to flash the TWRP thorugh the fastboot. It didn´t work. Everytime when the mobile was starting I finished on the screen that told me :"your device is unlocked...., your device is starting..." just the normal window when you have bootloader unlocked. I couln´t get into anything. I tried multiple twrps and then I found one called like twrp-3.1.1-1-frd.img https://forum.xda-developers.com/honor-8/development/twrp-t3566563 that worked for me and everything was ok.
But yesterday I wanted to unroot the phone. I read here how to do that: https://forum.xda-developers.com/honor-8/help/honor-8-to-stock-locked-t3509004
But everytime I wanted to start through stock recovery.img (that was downloaded in update.app from https://forum.xda-developers.com/honor-8/development/models-stock-firmware-packages-honor-8-t3501942) nothing happen.
Still the window with the message your device is starting. I coun´t get elwhere then bootloader mode. When I flashed the twrp-3.1.1-1-frd again, it worked normal. But I still wanted to get stock.
I didn´t know what to do so I scrolled down the same site and found this:
"Extract the update.app use this attachment
take Boot , Recovery , Data , System .
Go to ur Fast-boot Folder move this Files inside it .
Open Terminal or CMD throw Admin Rights inside the folder
make sure ur device with fast-boot mode before connecting ur cable to ur device
and make sure u have drivers installed
Type in CMD
Fastboot flash Boot boot.img
Fastboot flash Recovery Recovery.img
Etc .. flash all .imgs
Last type fastboot oem lock <YourPersonalUnlockCodeHere> ( THIS ONLY IF U LIKE TO LOCK AGAIN !)
fastboot Reboot . unplug cable and hope Work Fine ."
So I did what is written there I extracted those img files from update.app and flashed them ...... Now even if I put twrp-3.1.1-1-frd.img nothing happen I am stuck there only thing I can do is to boot to bootloader mode or be in the windew that is telling me device is starting....
And what would I want is to unstuck and go stock again.
Thank you in advance for your reply and sorry for the english.
How did I solve. I flashed twrp in recovery2 too, this solved it and mobile booted. THX for help guys.
https://forum.xda-developers.com/honor-8/how-to/discussion-t3591964/post72056001and#post72056001
deadko said:
https://forum.xda-developers.com/honor-8/how-to/discussion-t3591964/post72056001and#post72056001
Click to expand...
Click to collapse
I dont understand what you meant. the twrp-3.1.1-1frd.img doesn´t work for me at the moment it worked but since I did what I wrote it stopped working.
I cant get even in recovery mod.
Rommco05 said:
I always prefer clean start. Is a longest way but for performace and battery is the best!! So u can make downgrade to Marshmalow and your bootloader will locked (relocked) auto. If don't know how (xda search) leave a post here
Click to expand...
Click to collapse
But I don´t know how and where to start the only 2 screens I get is bootloader boot and your device is starting...
and I dont know why all of the TWRPs stoped working for me
Rommco05 said:
If u can boot to os. Please check in fastboot and in developer section >> frp is locked or unlocked? oem is...?
Click to expand...
Click to collapse
I can´t boot at all not even in recovery mode. "Phone onlocked, FRP unlock"
Rommco05 said:
Your last fw was?
edit: unroot phone? I see first time thx
Click to expand...
Click to collapse
When I rooted I installed how I wrote twrp, then flashed super su
I dont have unrooted phone I just wanted to unroot the way that I would install update.app throught stock recovery mode.
Markus37CZ said:
When I rooted I installed how I wrote twrp, then flashed super su
I dont have unrooted phone I just wanted to unroot the way that I would install update.app throught stock recovery mode.
Click to expand...
Click to collapse
U can install even with root . It will bring back all the files to stock .dont worry about current system. It will be updated with the file in update.app and all ur changes to system will be erased
Hi ppl. I need help bad! I accidentally erased my os. So when I try to flash a rom using the mi flash tool(which is amazing) it won't work because I have no operating system to enable USB debugging.so it says enable USB debugging but I can't. Any help would be appreciated TW RP installed unlock bootloader. Thanks in advance!!
just flash recovery rom using twrp then.
Way ahead of you..I tried to transfer several times,files,etc from my PC for some reason two stops halfway and doesn't copy them or move them. Only thing I haven't tried it is ADB sideload.. for some reason that never seems to work for me or work out the way I wanted to.
So twrp is flashed? Then yes try sideload. Also make sure your ADB is up to date as I've had that cause issues with large files and sideload before.
M.
dirtyrott3njb said:
Way ahead of you..I tried to transfer several times,files,etc from my PC for some reason two stops halfway and doesn't copy them or move them. Only thing I haven't tried it is ADB sideload.. for some reason that never seems to work for me or work out the way I wanted to.
Click to expand...
Click to collapse
Miflash doesn't need for usb debugging to flash rom I believe. It's all fastboot. If ur phone is not detected by pc, it means drivers.
It does indicate USB debuging not on. So yes it does . I've used it before to flash TWRP. The flash will also install the drivers before you use it so I can understand why it won't let me transfer anything from PC to phone when fastboot mode. It won't let me get past that stuff in this USB debugging is enabled. Frustrating brand new phone to only a couple weeks old.
Have you booted to twrp and format data (the one where you have to type "yes")?
Mi flash only required adb because it needs to run adb reboot fastboot. I'm in the States as well, PM me and maybe we can get this guy working over remote support. I haven't seen this issue myself, so I can't comment much.
Sent from my Mi MIX 2S using Tapatalk
@noobtoob,thx man. I can't format data because no keyboard is available for some reason. How can I pm you?
dirtyrott3njb said:
@noobtoob,thx man. I can't format data because no keyboard is available for some reason. How can I pm you?
Click to expand...
Click to collapse
Its all good. I'm about to pick up my kids from school, so let me head home, I'll PM you in a bit. We can use TeamViewer or something. If it comes down to it, I also have my work login to use for remote assist. You just need a semi up to date laptop or desktop computer.
Hopefully we can get this solved quickly. I'm unfortunately not in your immediate area, otherwise much easier hands on. The company I work for is down the street from your location however, I'm just a remote systems guy.
Sent from my Mi MIX 2S using Tapatalk
How do u know where I'm at?? Ok sounds good. Where do I look for you msg at?
dirtyrott3njb said:
How do u know where I'm at?? Ok sounds good. Where do I look for you msg at?
Click to expand...
Click to collapse
Tried to pm you but msg sent failed.
Only thing is for some reason I can't transfer anything for my PC to TW RP or my internal storage some reason just doesn't accept it and it's not my computer
I had the exact issue two days ago and the only thing that worked was to manually flash to stock. Since you already have the fastboot rom downloaded and extracted the hard work is done. What you need to do is to put all the files from that main folder (images) into a folder that you have adb installed. Then with your phone connected in fastboot open up a command prompt and once you have the directory set to where your fastboot is type the following and wait until each is done and says okay to move on.
fastboot flash modem modem.img
fastboot flash tz tz.img (I can't remember if this one actually flashed. I think it failed but it didn't matter)
fastboot flash logo logo.img
fastboot flash recovery recovery.img
fastboot flash system system.img (this one will take a long time to start flashing, don't worry. Also, there are about 5 files it will flash so be patient)
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot reboot
That puts you back to stock. I spent almost a whole night freaking out because I didn't have an OS and I couldn't get TWRP to reinstall. Once I did that and got things going I downloaded the same versions update on the phone (the one that can be flashed through the update page in settings) and did a flash of that as well.
sg01fc said:
I had the exact issue two days ago and the only thing that worked was to manually flash to stock. Since you already have the fastboot rom downloaded and extracted the hard work is done. What you need to do is to put all the files from that main folder (images) into a folder that you have adb installed. Then with your phone connected in fastboot open up a command prompt and once you have the directory set to where your fastboot is type the following and wait until each is done and says okay to move on.
fastboot flash modem modem.img
fastboot flash tz tz.img (I can't remember if this one actually flashed. I think it failed but it didn't matter)
fastboot flash logo logo.img
fastboot flash recovery recovery.img
fastboot flash system system.img (this one will take a long time to start flashing, don't worry. Also, there are about 5 files it will flash so be patient)
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot reboot
That puts you back to stock. I spent almost a whole night freaking out because I didn't have an OS and I couldn't get TWRP to reinstall. Once I did that and got things going I downloaded the same versions update on the phone (the one that can be flashed through the update page in settings) and did a flash of that as well.
Click to expand...
Click to collapse
The OP's issue was solved by just flashing TWRP, booting to it and sideloading the Stock ROM. I had the OP download the fastboot files as well, but we ended up not needing them.
Disclaimers:
> I am NOT encouraging anyone to do this. I'm not responsible for anything that happens to your device once you've rooted it already. I did this out of curiosity and I'm just sharing my experience.
> Also yeah, Rmx2040. Not Rmx2040EU.
> It's doable, but it is NOT stable. It boots but you can't use the phone normally. You know, like how you'd normally use a phone.
> I SOFTBRICKED MY PHONE.
Bugs:
UI Restarts every time you go landscape and go back to portrait
Can't open camera
UI Restarts every time you scroll on playstore or anywhere with lots of images
Phone lags, actually no, it restarts all the damn time
NOTES:
@Kraitos was looking for boot.img files so i decided to do a little digging too. I saw in a post somewhere that you need vbmeta.img and a patched (via magisk) boot.img from the device itself.
The "vbmeta.img" I used here was from a Realme 5. I figured all they 'kinda' looked the same plus I don't know if the file is also patched. I tried patching it in magisk but it didn't work, so I just grabbed a (patched?) vbmeta.img (from Realme 5 somewhere in the internet) and used that for our device which is, Rmx2040 (6i)
I grabbed the boot.img from the official ozip file in realme's site (From version A.27, I couldn't find any boot.img for A.31 because they haven't updated the link in the site yet). I opened it up, looked for it, grabbed it and patched it using magisk. Thankfully, it worked.
I used both the vbmeta.img (again, idk if it's patched) and the patched boot.img to root my device. I doubted it too, I thought it'll give me a bootloop or something, but it didn't.
If you want to do it, here are the steps:
Unlock your bootloader. Go here:
https://forum.xda-developers.com/realme-6i/how-to/unlocking-bootloader-realme-6i-rmx-2040-t4174255
Credits to @Kraitos for this awesome guide on how to unlock Rmx2040's bootloader.
If you're done unlocking your bootloader, download these files:
boot.img:
https://drive.google.com/file/d/1D7S9JGwDusyL6hJ6pWrFRBLo_9DdQLGR/view?usp=sharing
vbmeta.img:
https://drive.google.com/file/d/1Do2SfGI_Tp2jERcO77Vh1vEfjiQ6Xxe9/view?usp=sharing
Portable adb fastboot (if you don't have it yet):
https://drive.google.com/file/d/1m78UIsabMQlCvNIIv2e4xI19pN9b1otw/view?usp=sharing
Put all in one folder, it doesn't have to have a name.
Extract the zip file (minimal_adb_fastboot_1.4.3_portable.zip)
*Your folders should have the ff:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
boot.img
cmd-here.exe
Disclaimer.txt
fastboot.exe
vbmeta.img
Enable USB debugging in your phone.
Connect your phone to your pc.
Double click "cmd-here.exe"
Type the following in CMD:
adb reboot bootloader
If it displays a text in the middle, type "fastboot devices" on cmd. You SHOULD your phone's code there. If it doesn't display anything, replug the type C cable on your phone and type it again, do this until it shows.
Copy this and paste it in CMD:
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
Then press enter.
once it's done, copy this next:
fastboot flash boot boot.img
Then press enter.
Reboot your device by typing this in CMD:
fastboot reboot
If you've made it this far, you should install the latest Magisk Manager after you've unlocked the bootloader though. Or do it last, whatever you prefer works.
Viola, now you have an unstable phone.
I'm gonna try locking my bootloader later to flash the A.27 ozip later, I hope going back to "stock and unrooted" fixes the bugs I've experienced :|
I don't really know anything besides trying stuff out, I just wanted to see if it'll work properly with root. If anyone here noticed that I've done something wrong, please do tell me. I wanna try all the methods we can think of just so we can root this device.
Have a wonderful day y'all
Edit:
Everything went bad. I locked the bootloader because I needed access to stock recovery. It gave me a "red state"
I don't know how to fix this problem :|
Awesome guide and thanks for mention you know some people do that if you pay them to unlock bootloader and rooting device so this thread will be a savior to alot of people , I'll do testing in a couple of days asap i get a laptop relocking bootloader is mostly the same when you unlocked bootloader so it should be easy to flash stock again
Alright, so, quick update:
I tried to lock the bootloader while it had root (in my case, magisk). When I did, the phone went to "red state" (For those who don't know, it's basically bootloop wherein the phone never goes to recovery no matter what you do. Not even in stock).
Now, my phone is broken. It bootloops. I don't know what to do with this problem except going to a service center and have this fixed. Does anyone know how much it costs for reflashing stock rom to realme devices?
Sidenote: I tried the volume + down/up method to get into fastboot mode or stock recovery, but it never works. And honestly speaking, I don't think it will. To get into fastboot mode the bootloader needs to be unlocked, so that's crossed out AND I can't get into stock recovery because the phone restarts every 5 seconds because of that pesky "red state" thingy at the start.
Joesh.lucas said:
Alright, so, quick update:
I tried to lock the bootloader while it had root (in my case, magisk). When I did, the phone went to "red state" (For those who don't know, it's basically bootloop wherein the phone never goes to recovery no matter what you do. Not even in stock).
Now, my phone is broken. It bootloops. I don't know what to do with this problem except going to a service center and have this fixed. Does anyone know how much it costs for reflashing stock rom to realme devices?
Sidenote: I tried the volume + down/up method to get into fastboot mode or stock recovery, but it never works. And honestly speaking, I don't think it will. To get into fastboot mode the bootloader needs to be unlocked, so that's crossed out AND I can't get into stock recovery because the phone restarts every 5 seconds because of that pesky "red state" thingy at the start.
Click to expand...
Click to collapse
The problems you faced after rooting the phone is because you flashed an older version of boot.img thats why it wasn't working with latest rom and caused instability in system... And the second problem that you faced that red state thing..!! it was your fault you shouldn't relocked the bootloader with a patched boot img.. and if you wanted to boot the stock recovery you should have used the command " fastboot reboot recovery " this command in fastboot mode reboots the phone to recovery mode... Well i want to know what happend did your phone survived??
mehdi.shah said:
The problems you faced after rooting the phone is because you flashed an older version of boot.img thats why it wasn't working with latest rom and caused instability in system... And the second problem that you faced that red state thing..!! it was your fault you shouldn't relocked the bootloader with a patched boot img.. and if you wanted to boot the stock recovery you should have used the command " fastboot reboot recovery " this command in fastboot mode reboots the phone to recovery mode... Well i want to know what happend did your phone survived??
Click to expand...
Click to collapse
Thanks for the information, I now understand that I should use the same boot.img. It was worth the experiment tho, I just hoped I did it better so I wouldn't have to go through this process again.
My phone is here with me. It's still stuck on red state and I haven't went to a service center to have it fixed yet. I went to Hovatek to look for some ways to fix this problem. I tried using miracle box and the SP flashtool method but the latter had problems with the scatter file and the former didn't get past this:
Waiting for USB Port...
Set OPPO PreLoader USB VCOM (Android) (COM4)
>>Please Hold "ON" to connect with the phone...
I also looked a little bit more into it and I found out that I can use the OFP file and the flasher application here: https://firmwarex.net/realme-6i-rmx2040-official-firmware/
But unfortunately, I can't use the application because it's asking for an OPPO ID or something. Either I bring this phone to a service center or I'll just let it be this way until I decide to sell it somewhere. I hope I'll be able to fix this on my own tho, at least, someday.
Edit:
You can read more of my experience here:
Rmx2040 (realme 6i) scatter file
Hi guys, I'm trying to get the scatter file in this and so far I found this on the ozip file: preloader 0x0 pgpt 0x0 recovery_a 0x8000 misc 0x2008000 para 0x2088000 opporeserve1 0x2108000 opporeserve2
forum.hovatek.com
I'm subma rine13.
Joesh.lucas said:
Thanks for the information, I now understand that I should use the same boot.img. It was worth the experiment tho, I just hoped I did it better so I wouldn't have to go through this process again.
My phone is here with me. It's still stuck on red state and I haven't went to a service center to have it fixed yet. I went to Hovatek to look for some ways to fix this problem. I tried using miracle box and the SP flashtool method but the latter had problems with the scatter file and the former didn't get past this:
Waiting for USB Port...
Set OPPO PreLoader USB VCOM (Android) (COM4)
>>Please Hold "ON" to connect with the phone...
I also looked a little bit more into it and I found out that I can use the OFP file and the flasher application here: https://firmwarex.net/realme-6i-rmx2040-official-firmware/
But unfortunately, I can't use the application because it's asking for an OPPO ID or something. Either I bring this phone to a service center or I'll just let it be this way until I decide to sell it somewhere. I hope I'll be able to fix this on my own tho, at least, someday.
Edit:
You can read more of my experience here:
Rmx2040 (realme 6i) scatter file
Hi guys, I'm trying to get the scatter file in this and so far I found this on the ozip file: preloader 0x0 pgpt 0x0 recovery_a 0x8000 misc 0x2008000 para 0x2088000 opporeserve1 0x2108000 opporeserve2
forum.hovatek.com
I'm subma rine13.
Click to expand...
Click to collapse
Hey buddy i just rooted my realme 6i (RMX 2040) on build number A.37... everything went smooth and working flawlessly.... No system instabilities at all... Btw sorry to hear that your phone is still in brick state.. actually thing is oppo does not allow the users to flash stock rom on locked bl devices that why flasher tool asks for oppo authorized account in order to flash the device... And about SP flash tool.. it will not work either we have to wait for the patched rom that can be flashed on locked devices with sp flash tool
mehdi.shah said:
Hey buddy i just rooted my realme 6i (RMX 2040) on build number A.37... everything went smooth and working flawlessly.... No system instabilities at all... Btw sorry to hear that your phone is still in brick state.. actually thing is oppo does not allow the users to flash stock rom on locked bl devices that why flasher tool asks for oppo authorized account in order to flash the device... And about SP flash tool.. it will not work either we have to wait for the patched rom that can be flashed on locked devices with sp flash tool
Click to expand...
Click to collapse
Woah, is it true you've rooted it? How did you manage to pull it off? Is it similar to what I did except with different files?
Oh and yeah, I think I'll need to bring this to an authorized service center to have it fixed. In your currency, how much do you think it costs to flash the stock rom back to the phone? This has been a question that's been bothering me for months. I do hope it isn't pricey, because if it is then maybe I'll never have it fixed.
Joesh.lucas said:
Woah, is it true you've rooted it? How did you manage to pull it off? Is it similar to what I did except with different files?
Oh and yeah, I think I'll need to bring this to an authorized service center to have it fixed. In your currency, how much do you think it costs to flash the stock rom back to the phone? This has been a question that's been bothering me for months. I do hope it isn't pricey, because if it is then maybe I'll never have it fixed.
Click to expand...
Click to collapse
Yeah the procedure was the same as yours... I unlocked the bootloader i was on A27 build... And i downloaded the latest ozip file from the official site and i opened it up in file manager it asked if i want to update the software i clicked yes.. and it rebooted to stock recovery and started updating the device.. after successful update i opend up the ozip file by renaming it to .zip and extracted the boot.img and vbmeta.img. i patched the boot.img with latest magisk manager and tha than flashed those files in fastboot mode... With same commands that u used... And everything went well and its all good and rooted no problem at all..
And yeah the service center thing.. if its the software issue than the charge around 1.5 to 2k rupees in my country...which is around 9.34 to12.4 US dollars..
mehdi.shah said:
Yeah the procedure was the same as yours... I unlocked the bootloader i was on A27 build... And i downloaded the latest ozip file from the official site and i opened it up in file manager it asked if i want to update the software i clicked yes.. and it rebooted to stock recovery and started updating the device.. after successful update i opend up the ozip file by renaming it to .zip and extracted the boot.img and vbmeta.img. i patched the boot.img with latest magisk manager and tha than flashed those files in fastboot mode... With same commands that u used... And everything went well and its all good and rooted no problem at all..
And yeah the service center thing.. if its the software issue than the charge around 1.5 to 2k rupees in my country...which is around 9.34 to12.4 US dollars..
Click to expand...
Click to collapse
Does root work as it should?
Russian community guys reported that root exists in the system but not works at all. Rooting procedure looks the same.
sqzd0 said:
Does root work as it should?
Russian community guys reported that root exists in the system but not works at all. Rooting procedure looks the same.
Click to expand...
Click to collapse
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
mehdi.shah said:
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
Click to expand...
Click to collapse
I don't mean to be rude but, can you make a thread for that? Some rmx 2040 owners want to root their device and I think i just gave them a recipe for disaster.
Oh and by the way, thanks for answering my question. I have another one, will it be okay to update your device whilst rooted? If so then how do you stop the auto update?
(Sorry for the questions man hahahaha I wanted the same outcome but I failed miserably :| )
mehdi.shah said:
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
Click to expand...
Click to collapse
Bro give me boot.img a37
mehdi.shah said:
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
Click to expand...
Click to collapse
Give me boot.img of a37 version
mehdi.shah said:
Hey buddy i just rooted my realme 6i (RMX 2040) on build number A.37... everything went smooth and working flawlessly.... No system instabilities at all... Btw sorry to hear that your phone is still in brick state.. actually thing is oppo does not allow the users to flash stock rom on locked bl devices that why flasher tool asks for oppo authorized account in order to flash the device... And about SP flash tool.. it will not work either we have to wait for the patched rom that can be flashed on locked devices with sp flash tool
Click to expand...
Click to collapse
If you rooted dump the stock recovery and boot.img through terminal emulator I will try to port twrp
Boot.img and Vbmeta file can now be accessed by clicking the text above
Do is still need to relock my bootloader inorder to downgrade to A.27 update ? Thanks
mehdi.shah said:
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
Click to expand...
Click to collapse
Bro i tried the rooting process and i didnt check the boot and i rooted my phone the wifi,blueooth, camera, etc doesnt work anymore. If POSSIBLE can i revert it back to normal?
Can anyone provide me a twrp recovery file for realme 6i rmx2040 A.47 plsss