Related
Hi,
2 weeks ago I got my P8000 from the german elephone distribution, it came with android 6. It seems to be an other version of the phone, the fingerprint sensor has moved up near the camera.
So my problem is, that I can't find a working rom for this device. I tried to root the phone and after that it did not boot anymore, so I tried to flash the 6.0 stock rom but the screen is white with moving stripes.
Where can I get a working rom for my phone?
Nobody with a new version phone who could take a dump for me?
flo1k said:
Nobody with a new version phone who could take a dump for me?
Click to expand...
Click to collapse
I think you should ask elephone (on facebook or some other social medias) for a dump, I don't see any chances that there are many people out there that own the 2016 version... :/
I wrote to the elephone facebook contact but they just pointed me to the BBS with the not working 'old' Rom file.
So if I could get another new P8000 would it be easy to take a dump oft it and flash it to my phone?
flo1k said:
I wrote to the elephone facebook contact but they just pointed me to the BBS with the not working 'old' Rom file.
So if I could get another new P8000 would it be easy to take a dump oft it and flash it to my phone?
Click to expand...
Click to collapse
I think you won't have to buy a new device, just point out to them that, that rom on the forum is for the old version and it's not working for your's. I hope they'll provide it for you.
Hey!
I just received this version and would be willing to take the dump, but I don't know how.
MTKDroidTools says unknown rom structure and doesn't allow me to do it.
Any tips?
Emile
Hey Emileh these are great news! I cannot help you with this, but surely someone here can!
Many thanks,
Flo
flo1k said:
Hi,
2 weeks ago I got my P8000 from the german elephone distribution, it came with android 6. It seems to be an other version of the phone, the fingerprint sensor has moved up near the camera.
So my problem is, that I can't find a working rom for this device. I tried to root the phone and after that it did not boot anymore, so I tried to flash the 6.0 stock rom but the screen is white with moving stripes.
Where can I get a working rom for my phone?
Click to expand...
Click to collapse
install niew rom
vagca said:
install niew rom
Click to expand...
Click to collapse
Sorry, I don't understand
I have at least two P8000(B) - and bricked one of them see this post:http://forum.xda-developers.com/elephone-p8000/help/stock-rom-p8000b-t3434477
The good news are: I still have a working one and could use this as a source to generate a firmware file... if someone could tell me how
I think I have to do the procedure with the SP Flashtool because the display of the faulty phone is not usable
FrauHofrat said:
I think I have to do the procedure with the SP Flashtool because the display of the faulty phone is not usable
Click to expand...
Click to collapse
Same as mine. The display controller seems to be another one.
I'm guessing thats just a kernel problem, right? The drivers in the kernel?
FrauHofrat said:
I have at least two P8000(B) - and bricked one of them see this post:http://forum.xda-developers.com/elephone-p8000/help/stock-rom-p8000b-t3434477
The good news are: I still have a working one and could use this as a source to generate a firmware file... if someone could tell me how
I think I have to do the procedure with the SP Flashtool because the display of the faulty phone is not usable
Click to expand...
Click to collapse
P8000B is almost impossible to brick. If you install SP flash, and download the correct recovery (like TWRP), and the correct version ROM's with scatter.txt you can recovery the phone in just about any circumstance. I put the P8000B recovery files on my PC, Formatted whole flash and bootloader. After that, the phone was bricked, and wouldn't turn on. Loaded the P8000B system recovery scatter.txt, and SP flash installed it perfectly. Booted fine. With SP flash it's almost impossible not to be able to restore the P8000B as long as you have proper files,
kgoerbig said:
P8000B is almost impossible to brick. If you install SP flash, and download the correct recovery (like TWRP), and the correct version ROM's with scatter.txt you can recovery the phone in just about any circumstance. I put the P8000B recovery files on my PC, Formatted whole flash and bootloader. After that, the phone was bricked, and wouldn't turn on. Loaded the P8000B system recovery scatter.txt, and SP flash installed it perfectly. Booted fine. With SP flash it's almost impossible not to be able to restore the P8000B as long as you have proper files,
Click to expand...
Click to collapse
This is mainly correct, but....
With SP flash it's almost impossible not to be able to restore the P8000B as long as you have proper files,
Click to expand...
Click to collapse
there is no Stock ROM, no scatter file and I think not even a TWRP or Philz Recovery available for the 'new version' of the P8000 - I call it P8000(B) because it is written on the box of the phone.
Emileh made a good description of the problem here: http://forum.xda-developers.com/elephone-p8000/general/2016-version-fingerprint-scanner-t3436270
But you could help us if you can provide the necessary files....
Is it the us version? It's the same one I have. I'll post a video how to soon
******EDIT******
FrauHofrat, sorry I did not realize that there was a "Rev.2" out for the P8000 US Version. I am surprised Elephone hasn't released a flash-able version for SPflash yet. Honestly, it would be in their best interest to ship any Rev of their US versions w/ TWRP and freely distributing flash-able images/scatter.txt, so if it gets bricked during a failed OTA update, folks would not have to send their phones back to be fixed. I have the Rev 1 of that phone.
Any word on the Elephone forum regarding the Rev. 2 version for images/scatter.txt? I will keep an eye out. Is there any specific model related info that shows up in About Phone, or written on the box/battery?
Sent from my p8000 using Tapatalk
We're not talking about the P8000-B here, which I believe has different LTE bands so it's better suited for the USA
We're talking about P8000 6.0, which is the newer version of the phone that's currently being shipped in Europe. It has some small technical changes and stock Android 6
Edit: by the way, the box does say P8000(B), but I don't really trust that description
Hi guys,
I was just looking at the elephone forum and found this: http://bbs.elephone.hk/thread-11929-1-1.html#.V7WrLDWbfSY . There's the stock rom link for the 2nd revision of the P8000, so hope you can get it working properly again.
@ardrift
Thank you for this information - the ROM works and the phone is alive again!
But there is still one thing to do: because of flashing the wrong firmware my phone lost the IMEI. This should'nt be a problem on rooted devices but the stock ROM resists all attempts to be rooted
FrauHofrat said:
@ardrift
Thank you for this information - the ROM works and the phone is alive again!
But there is still one thing to do: because of flashing the wrong firmware my phone lost the IMEI. This should'nt be a problem on rooted devices but the stock ROM resists all attempts to be rooted
Click to expand...
Click to collapse
Can you try dialing *#*6813#*#* in the stock dialer app? Someone on the elephone forum has written this as a solution, altough I don't know if it works, or how would it work... If you are stuck you can upload a screenshot, I can look at it
PS: Your IMEI numbers should be sticked on your battery, you can see them if you remove the phone's back.
Change IMEI on P8000
@ardrift:
first I thought this is a joke but actually it worked :victory:
with *#*#6813#*#* entered on the stock dialer you can acess the "IMEI-Tool" which allows you to enter a new IMEI for both SIM cards. The new IMEI stay permanent even after reboot and this also works on 'old' P8000.
Sometimes life can be so easy
Dear Community,
I just searched the past 2 days for a solution but I've not been lucky
Therefore I'd like to ask for help in this forum and hope there is some additional hint or hack I could try...:
So here's the situation:
OnePlus 5T (8/128) with a non booting or not "useful" OS (see last point what I've tried)
No TWRP or CWM
Stock Recovery present
Bootloader Locked
Allow Bootloader to be unlocked = FALSE
What I've already tried yet:
Flashing TWRP --> Not possible Bootloader Locked
Flashing regarding any other kinds like "update" or "flash all" as provided with TOOL_ALL_IN_ONE
ADB Sideload any available ROMS (Original "full" OP5T / FreedomOS / Omni8) --> ADB stops at 47% in Stock Recovery regardless of size of the ZIP file
Tried different versions of ADB (32 & 64 Bit / older & new / also with the LargeAddressAware approach / and on multiple PC's) --> Always same error (47%)
Stumbled upon the possibility to EmergencyDownload a factory flash due to Qualcomm chipset using the MSM-Download-Tool --> Only OnePlus 5 ROM available (no "T")
Mentioned EDL procedure works and OS is booting BUT neither Touchscreen nor USB OTG (for external mouse support) is working --> So I can't navigate and allow Bootloader to be unlocked again
Unfortunately I'm now stuck and have no more idea how to unbrick my phone again
What would help:
Any source to MSM-Download-Tool packed with a correct ROM for the OnePlus 5T
A Workaround to just flash TWRP via MSM-Download-Tool or Qualcomm's QFIL application in EDL mode
Some "hack" to bypass the locked Bootloader situation
Every appreciated Input you might have that I'm currently not aware of...
So PLEASE let me know of any approach that I could try or if you might have found a link or something else to a solution that might help me out of this disaster...
Many thanks in advance!
Tryouts due to your feedback:
@dreinulldrei - "fastboot boot recovery.img" tried with the original 5T Recovery.img also with blu_spark TWRP --> no luck...
SOLVED SOLUTION:
As the EDL factory flash ROM is currently not (or will never officially be) available public getting in contact with the OnePlus support team is required.
They have such a recovery tool (MSM-Download-Tool) with an appropriate ROM and are able to flash the device during a remote support session conducted via chat.
So by starting a chat on the OnePlus Support page and describing your situation will lead to scheduled time slot where a Level-2 technician will do all required steps remotely.
(All files are password protected and the technician ensures they are deleted at the end of the session so I'm unfortunately not able to provide the sources for DIY purposes...)
Following. I would think there would be some way to flash some sort of signed image via fastboot...
U flashed a 5 os to it, using the msmtool try to extract those files from 5t os, I will do it when I get home and so u can try it, i can't guarantee anything though, would u like me to do that for u
Bradl79 said:
U flashed a 5 os to it, using the msmtool try to extract those files from 5t os, I will do it when I get home and so u can try it, i can't guarantee anything though, would u like me to do that for u
Click to expand...
Click to collapse
Thanks for your input - I'm really not aware of how to generate such *.ops ROM files as this is what the MSM Tool expects...
But if there is a way and you are able to extract and produce a MSM flashable file I would be very happy to try!
I would recommend trying to boot a OP5T recovery, you might have flashed some OP5 rom including OP5 recovery. Just go into fastboot (power on with volume up pressed down), then via cmd:
fastboot boot recovery.img
Since OP does not offer the recovery to be downloaded, it will need to be downloaded from a working device. Lacking the cable right where I am, but I am sure someone else can help out.
crakerjac said:
Following. I would think there would be some way to flash some sort of signed image via fastboot...
Click to expand...
Click to collapse
Thanks for the input - I forgot to mention I also tried the 2 original available OP5T "full" ZIP ROM's (think they should be signed...)
Will add this to the initial Post but I assume also no chance here...
dreinulldrei said:
I would recommend trying to boot a OP5T recovery, you might have flashed some OP5 rom including OP5 recovery. Just go into fastboot (power on with volume up pressed down), then via cmd:
fastboot boot recovery.img
Since OP does not offer the recovery to be downloaded, it will need to be downloaded from a working device. Lacking the cable right where I am, but I am sure someone else can help out.
Click to expand...
Click to collapse
Ohhh good point - I also think there is the "wrong" recovery (from 5) currently on my phone (because also there the touchscreen behaves unexpectedly...)
But unfortunately with your command I get the "Your device is corrupted. It can't be trusted and will not boot" message.
Tried this with the original 5T Recovery.img I managed to obtain and also with the blu_spark TWRP - no luck...
Edit: Ignore, misread previous post.
U may have to make a call to oneplus so they can restore for u
Submit a ticket to One Plus
You are going to have to submit a ticket, they will arrange a time to help you by unbricking the phone remotely.
I just had to do this myself this week, and it got done today.
I do have the 5t unbricking files but I cannot access the archive because it's password protected.
One important this you didn't mention is how this happened.
OnePlus may be able to help with this one, but all root guides explicitly include the phrase "at your own risk."
blackknightavalon said:
OnePlus may be able to help with this one, but all root guides explicitly include the phrase "at your own risk."
Click to expand...
Click to collapse
Bradl79 said:
U may have to make a call to oneplus so they can restore for u
Click to expand...
Click to collapse
WMerkens said:
You are going to have to submit a ticket, they will arrange a time to help you by unbricking the phone remotely.
I just had to do this myself this week, and it got done today.
I do have the 5t unbricking files but I cannot access the archive because it's password protected.
Click to expand...
Click to collapse
Thanks for all your advice - so I will arrange a support chat/ticket as soon as possible and inform about the result in this thread.
Didn't thought that OnePlus Support Team would even care about such bricks (no warranty / own risk / "playing" with root / etc...)
But as indeed they seem to help like @WMerkens experienced I would be very happy to have a working device again
CodeXter said:
Thanks for all your advice - so I will arrange a support chat/ticket as soon as possible and inform about the result in this thread.
Didn't thought that OnePlus Support Team would even care about such bricks (no warranty / own risk / "playing" with root / etc...)
But as indeed they seem to help like @WMerkens experienced I would be very happy to have a working device again
Click to expand...
Click to collapse
don't know why you would think that OP wouldn't help...they have said from day one that unlocking/rooting does not void your warranty. Heck they encourage it. I assume you are the same person on the OP forum w/ this problem. Hopefully after you get this resolved you will have learned to NEVER EVER RELOCK your phone unless you do the whole factory image qualcomm recovery tool bit. and experienced OP folks on this forum know any claims of a "hardbricked" OP phone is ALWAYS not true.
Yeah oneplus used to be good about and does a remote session to restore, this was back in the one plus one days though, but I think they still do it
---------- Post added at 03:25 AM ---------- Previous post was at 02:54 AM ----------
WMerkens said:
You are going to have to submit a ticket, they will arrange a time to help you by unbricking the phone remotely.
I just had to do this myself this week, and it got done today.
I do have the 5t unbricking files but I cannot access the archive because it's password protected.
Click to expand...
Click to collapse
Awwww I wish we could get them, do they use the msmtool too?
How I bricked a 5t
I got the phone and I had installed twrp, that went fine. I was looking at magick systemless rooter when the phone then kicked in with a OTA update, I chose to ignore it the first time. It occurred again a few minutes and in my haste I let it do it's job but it did not complete correctly. I rebooted and the phone complained about corruption to the OS, I got in again but made the dumb mistake of re enabling the OEM lock and because I thought that might be causing the problem. I rebooted again but now I could not boot any more into the OS, it complained I was corrupted and go to google to see what to do.
So I was left with a bricked phone.
I could do bootloader but not recovery and I could not unlock the bootloader.
I could not get in via adb usb debug, So after much research I download the OnePlus 5 unbricking pack and learned a whole lot about qualicom and EDL mode, plus I learned a lot about the QFIL tools and restoring a phone. I did the 5 unbrick but my screen ended up upside down but the touch was right side up, which resulted in a very hard to use phone.
I tried the QFIL method but I was missing a mdb file to be able to talk to the phone.
So I gave up submitted a ticket and after much bad co-ordination on their part got a level 2 tech to debrick the phone remotely.
They do a reverse VPN and connect to your computer, they tell you to have 2 files archive ready in a folder on your desktop (they supply the links). They install the EDL driver and unpack the debrick archive. The archives are password protected, they run the tool and restore the phone
back to factory.
They erase the unpacked archives after they are done.
jerrywmilton said:
don't know why you would think that OP wouldn't help...they have said from day one that unlocking/rooting does not void your warranty. Heck they encourage it. I assume you are the same person on the OP forum w/ this problem. Hopefully after you get this resolved you will have learned to NEVER EVER RELOCK your phone unless you do the whole factory image qualcomm recovery tool bit. and experienced OP folks on this forum know any claims of a "hardbricked" OP phone is ALWAYS not true.
Click to expand...
Click to collapse
Oh yes I've learned my lesson on this :angel: --> Never ever set OEM to be unlocked to NO again
Obviously I do not exactly know what wrong procedure made me stuck in this situation but I just wanted to revert every single step back one by one to see which element brings me back to a valid SafetyNet situation...
I've been with the OnePlus "family" since the OP1 but never needed any direct support from the vendor - so every time there's a first time and so for me now...
Thus I really didn't know OP staff is actively doing remote support for their devices - but thumbs up for that! :good:
(BTW: I'm not the guy from the OP forum)
Bradl79 said:
Yeah oneplus used to be good about and does a remote session to restore, this was back in the one plus one days though, but I think they still do it
---------- Post added at 03:25 AM ---------- Previous post was at 02:54 AM ----------
Awwww I wish we could get them, do they use the msmtool too?
Click to expand...
Click to collapse
Yes basically it's the same archive as the 5 unbrick pack but it's for 5t, OnePlus 5T OxygenOS 4.7.2-171116.zip is the archive and you can look in it and you see the ops file is for dumpling not cheesburger, which is the code name for 5t. I saw the MsmDownloadTool is 4.0.8
Bradl79 said:
Yeah oneplus used to be good about and does a remote session to restore, this was back in the one plus one days though, but I think they still do it
---------- Post added at 03:25 AM ---------- Previous post was at 02:54 AM ----------
Awwww I wish we could get them, do they use the msmtool too?
Click to expand...
Click to collapse
I just had a chat with them before and got mailed a link to the MSMTool incl. ROM for the OP5T (dumpling)
But unfortunatley support files from OnePlus are password protected Nevertheless here the original vendor link:
https://onepluscn-my.sharepoint.com/personal/sheva_liu_oneplus_net/_layouts/15/guestaccess.aspx?docid=0fde9596c72744b4fb9c073ca5d87edbe&authkey=AQPXKRi7pdIzZX-5WH_pwWg&e=1030aa0046da4d1aa9189020027d9c93
So I have to wait for my remote support schedule on Saturday to have the L2 technician entering the password and do the rest.
Would be able to do this myself but OnePlus obviously wants to protect their sources what I have to accept, respect and be patient for...
So, never turn off the OEM Unlocking?
hi,
A70 is now widely sold, i try to buy one soonest but just waiting for root and twrp. it is still empty here on xda...
i found a link show how to root and install
https://myphoneupdate.com/samsung-galaxy-a70-twrp-recovery/
can i ask if some one already tried as above? looks like a copy method for all kind of phones ...
tks.
Most likely fake, the article was published a month ago. A70 only got released on 26th March.
I would definitely wait until someone posts a technique here; I tend to trust the experts here, but not so much everywhere else on the internet. I would prefer to wait a few weeks and put with an unrooted device, rather than possibly end up with a bricked (or hijacked) device.
Andre
ok i will wait...
it was like this, waited for s10+, came twrp but didnot like camera hole and waiting for A70, then waiting for twrp, then oneplus7pro release, then wait a bit for its twrp, till then note 10 pro comes soon, then wait for twrp of it....
and after 2+ year still using note8 LOL
amk said:
hi,
A70 is now widely sold, i try to buy one soonest but just waiting for root and twrp. it is still empty here on xda...
i found a link show how to root and install
https://myphoneupdate.com/samsung-galaxy-a70-twrp-recovery/
can i ask if some one already tried as above? looks like a copy method for all kind of phones ...
tks.
Click to expand...
Click to collapse
First thing I tried ofcourse, rooting the A70, but... follow the steps in the manual yourself, and you'll see that you get stuck on step 3:
3.) After That Download TWRP Recovery https://twrp.me File On Your PC And Renamed The Downloaded Recovery File Name To twrp.img.
But there is no TWRP Recovery available for the A70
I also tried the A50 manual, but that also fails (stuck on OEM lock). I can install CROM Service, but it crashes.
Captain Beretta said:
First thing I tried ofcourse, rooting the A70, but... follow the steps in the manual yourself, and you'll see that you get stuck on step 3:
3.) After That Download TWRP Recovery https://twrp.me File On Your PC And Renamed The Downloaded Recovery File Name To twrp.img.
But there is no TWRP Recovery available for the A70
I also tried the A50 manual, but that also fails (stuck on OEM lock). I can install CROM Service, but it crashes.
Click to expand...
Click to collapse
don't follow some clickbait website's...
wait for a proper and trusted dev to release twrp. the phones has barely hit the market it will take a few weeks (if not months) at least till someone builds an twrp. one think you could provide us with would be some information. is the bootloader unlockable?
In devsettings is a possible to unlock oem. Try this before flashing twrp. If twrp flashed ok, I think need to wipe all data, include internal storage, then flash DM-VERITY, FORCE ENCRYPTION, AND DISC QUOTA DISABLER
zackptg5.com/android.php
I don't try it by myself. But you can try it, if you just buy the phone, and have not important data on it
What about this guide is it worth trying or not really possible? https://topjohnwu.github.io/Magisk/install.html
Avicohen21 said:
What about this guide is it worth trying or not really possible? https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
Need to try
hello everyone I find a good deal on galaxy a70 is anyone succeed in rooting?
celoxocis said:
... is the bootloader unlockable?
Click to expand...
Click to collapse
i have opened 2 sealed box of A70 and there was no OEM unlock option in developer mode. then got another with tick to choose. baterry is so good but look like i have touch panel issue. waiting for update and then root, twrp...
amk said:
i have opened 2 sealed box of A70 and there was no OEM unlock option in developer mode.
Click to expand...
Click to collapse
Mine (bought direct from Samsung UK) has the OEM Unlock option in the Developer Options menu. Not tried it yet, not really much point until there is a reliable and tested root out there.
Andre
Hey guys manegd to root with this guide https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Seems to work good I'll notify if I'll notice any bugs. If you have twrp porting guide send me and I'll try to Port. If you want I can open a new thread with more details and upload the AP file I used. BTW I have the Israeli version SM-705FN
Avicohen21 said:
Hey guys manegd to root with this guide https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Seems to work good I'll notify if I'll notice any bugs. If you have twrp porting guide send me and I'll try to Port. If you want I can open a new thread with more details and upload the AP file I used. BTW I have the Israeli version SM-705FN
Click to expand...
Click to collapse
make a topic please
sanakess said:
make a topic please
Click to expand...
Click to collapse
Ok when I get home I'll open a thread with detailed explanation of what I did
Samsung account
Hello. My dumbass bought used A70 with samsung account. I can't make a factory reset, because it needs password from old owner account which i don't know. But I have my Google account on that phone and Google find my device enabled. Will I need to enter samsung account information when I make a reset via Google find my device? So when reset is made, phone will be locked only by FRP? And then when I login in my old Google account can i create a new Samsung account or do I need to login in existing that was on that phone first? Sorry for offtopic.
Any news about TWRP? SuperSu or Magisk?
Hello All, still can't find TWRP for sm-a705fn
Can I flash TWRP for another Exynos phone, like Galaxy 9, to my A70 ?
Also, can I still use SuperSu with Pie/A70 ? I failed to root my previous Galaxy Tab8 with custom Pie using SuperSU, had to root with Magisk instead,
it worked just fine, but the link to topjohnwu mentioned in previous posts, tells scary things about Samsung/Pie/Magisk -
like, I have to switch between two recoveries... Is that really the case?
I haven't noticed any issue with Tab8/Pie/Magisk, but SuperSu would be still more familiar to me.
used2brick said:
Hello All, still can't find TWRP for sm-a705fn
Can I flash TWRP for another Exynos phone, like Galaxy 9, to my A70 ?
Also, can I still use SuperSu with Pie/A70 ? I failed to root my previous Galaxy Tab8 with custom Pie using SuperSU, had to root with Magisk instead,
it worked just fine, but the link to topjohnwu mentioned in previous posts, tells scary things about Samsung/Pie/Magisk -
like, I have to switch between two recoveries... Is that really the case?
I haven't noticed any issue with Tab8/Pie/Magisk, but SuperSu would be still more familiar to me.
Click to expand...
Click to collapse
No, you can't use twrp for a different device, and don't use SuperSU neither. It was sold by chainfire to a Chinese company years ago and have been basically abandoned since 2017. I'm pretty sure Magisk is the better choice on any device running android 5 - 9.
Sent from my motorola one vision
Hello,
The problem with the post you mentioned is that there is no valid twrp attached. And I noticed that only Odin detects the fastboot mode of this device. If you enable USB debugging let's say, the command "adb devices" will detect the device and list it; whereas, if you reboot it to bootloader mode(fastboot), the command fastboot devices doesn't detect the phone. So in fastboot mode, only Odin will detect the device. Meaning, that the post of fake and not tested.
Regards,
Wael
amk said:
i have opened 2 sealed box of A70 and there was no OEM unlock option in developer mode. then got another with tick to choose. baterry is so good but look like i have touch panel issue. waiting for update and then root, twrp...
Click to expand...
Click to collapse
That's weird. I do have the Bootloader unlock option in the developer settings and can do/undo it just fine. Looks like Samsung is using different Firmware versions on the A70?
Just got a Redmi Note 8 Pro with Global ROM and discovered that call recording won't work due to Google/Android Pie limitations.
After some searching, I found (on this forum) that the Indonesia ROM supports call recording on this phone.
Here are my questions:
1. Will burning a different ROM affect my warranty?
2. Will I lose any functionality by switching from Global to Indonesia ROM, and if so, what? Specifically, will NFC functionality be affected?
3. If I ever do a factory reset, will the phone revert to Global ROM?
4. I found the Indonesia ROM files here. There are three files called Recovery, OTA, and Fastboot. Do I need them all? If so, do they need to be burned in any specific order?
5. Where can I find complete instructions for burning the Indonesia ROM? I am new to Xiaomi, and the last time I burned a ROM to a phone was 5 years ago (Samsung); I don't remember anything, so I'd like instructions that assume nothing and don't skip any steps (instructions for intelligent dummies). I found these instructions for installing TWRP, but there's nothing about what to do next, and there's a list of pre-requisites with no explanations (Unlocked Bootloader, Phone Drivers, ADB and Fastboot Drivers), making the instructions insufficient for a noob like me.
Thanks much.
yossidme said:
Just got a Redmi Note 8 Pro with Global ROM and discovered that call recording won't work due to Google/Android Pie limitations.
After some searching, I found (on this forum) that the Indonesia ROM supports call recording on this phone.
Here are my questions:
1. Will burning a different ROM affect my warranty?
2. Will I lose any functionality by switching from Global to Indonesia ROM, and if so, what? Specifically, will NFC functionality be affected?
3. If I ever do a factory reset, will the phone revert to Global ROM?
4. I found the Indonesia ROM files here. There are three files called Recovery, OTA, and Fastboot. Do I need them all? If so, do they need to be burned in any specific order?
5. Where can I find complete instructions for burning the Indonesia ROM? I am new to Xiaomi, and the last time I burned a ROM to a phone was 5 years ago (Samsung); I don't remember anything, so I'd like instructions that assume nothing and don't skip any steps (instructions for intelligent dummies). I found these instructions for installing TWRP, but there's nothing about what to do next, and there's a list of pre-requisites with no explanations (Unlocked Bootloader, Phone Drivers, ADB and Fastboot Drivers), making the instructions insufficient for a noob like me.
Thanks much.
Click to expand...
Click to collapse
Hey,
Before going any further you first need to make sure what region is your phone. Is it a Chinese phone (bought from AliExpress for example) or a real Global phone (bought from a local store/official retail). Because you could very well own a Chinese phone shipped with a Global Rom flashed on it and this could result in some problems for you in terms of what you can do with it and how you can do it.
If you bought/received a phone with already unlocked bootloader, you should return it.
Unlocking bootloader should only be done by you when you need it.
1. Technically unlocking bootloader, ESSENTIAL step prior flashing anything, void your warranty.
However and that's what is interesting, if at some point you decide to flash back your original region rom (here Global) and lock back bootloader, none will know but Xiaomi servers you once unlocked this device certainly not a local reseller. So in term of warranty you should be safe, that is of course unless you brick your phone doing stuff you were not supposed to do with a locked bootloader if you are following.
2. If not mistaking, I think you loose NFC. Indian phones for sure do not have NFC at all, for their version, the chip was replaced with a 2nd SIM card tray (not shared). Not sure if you read the functionality afterward using rooted tricks.
3. No that does not work this way. When you are running a Rom, any version, if you factory reset that room, you just return to installation screen of that given Rom.
To return to Global Rom, you will need to reflash that Global Rom using the same method you did successfully flashing the Indonesian Rom (or any other rom) for example.
Would be wise to first download the exact version of the Rom you are currently using on your phone for archives purpose (BURN IT on good quality medias!) to revert back to it when/if needed. You can also archives OTA updates of that version you may not have taken yet to apply them manually if you ever revert back to that Global Rom and want to.
4. Different versions depends on what you are doing. In your case Fastboot version is what you need at the moment. You can find all different kind of versions of Roms for your RN8PRO on that site
As for the way to flash them, order and everything, you will need to look for guides online,
I dont think any order matters, just make sure to flash them all before rebooting disconnecting device. But if you are unsure of what you are doing, you'd be probably best using a tool such as MiFlash.
5. Here you can find one from the MIUI community website guiding you through the use of MiFlash to flash a stock Rom on your device.
Just note you do not have to use any tools to flash the .images of all partitions, you can easily doing it from command line using fastboot flash command one after an other.
Also note that installing TWRP is usually not needed to flash stock Roms (unlike flashing custom roms). Trying to mess up with the recovery partition is actually what seem to brick most of the devices.
However please note UNLOCKING your BOOTLOADER is MENDATORY.
Hope this helps.
Regards,
doesnt matter if you switch to any rom variant .i have switched mine to indonesian ,europe and indian and alll worked fine execpt indian version felt a bit laggy .just download the fastboot version of the rom and flash it through mi flash tool xiaomiflash .your bootloader needs to be unlocked and dont forget to check cleann all button in mi flash and dont check clean and lock
I have got global version and changed imei with unlocked bootloader. Can i flash indonesian rom without lose f my imei?
Thanks in advance for your answers
Muad.Dib,
Thanks for your detailed reply.
If I understand correctly, unlocking the bootloader voids the warranty just the same as rooting the phone, so if all I want is to get call recording, I may as well just root the phone and save the bother of flashing a different ROM.
Does that make sense to you, or do you see any advantage to flashing a different stock ROM instead of just rooting the phone? From past experience I've seen that rooting has additional benefits anyway.
BTW, I bought my phone on Banggood. It was advertised as Global ROM, and that appears to be what it has. As soon as I turned the phone on it updated to MIUI Global 11.0.2.1; I don't know what version it was before the update.
Muad.Dib said:
Hey,
Before going any further you first need to make sure what region is your phone. Is it a Chinese phone (bought from AliExpress for example) or a real Global phone (bought from a local store/official retail). Because you could very well own a Chinese phone shipped with a Global Rom flashed on it and this could result in some problems for you in terms of what you can do with it and how you can do it.
If you bought/received a phone with already unlocked bootloader, you should return it.
Unlocking bootloader should only be done by you when you need it.
1. Technically unlocking bootloader, ESSENTIAL step prior flashing anything, void your warranty.
However and that's what is interesting, if at some point you decide to flash back your original region rom (here Global) and lock back bootloader, none will know but Xiaomi servers you once unlocked this device certainly not a local reseller. So in term of warranty you should be safe, that is of course unless you brick your phone doing stuff you were not supposed to do with a locked bootloader if you are following.
2. If not mistaking, I think you loose NFC. Indian phones for sure do not have NFC at all, for their version, the chip was replaced with a 2nd SIM card tray (not shared). Not sure if you read the functionality afterward using rooted tricks.
3. No that does not work this way. When you are running a Rom, any version, if you factory reset that room, you just return to installation screen of that given Rom.
To return to Global Rom, you will need to reflash that Global Rom using the same method you did successfully flashing the Indonesian Rom (or any other rom) for example.
Would be wise to first download the exact version of the Rom you are currently using on your phone for archives purpose (BURN IT on good quality medias!) to revert back to it when/if needed. You can also archives OTA updates of that version you may not have taken yet to apply them manually if you ever revert back to that Global Rom and want to.
4. Different versions depends on what you are doing. In your case Fastboot version is what you need at the moment. You can find all different kind of versions of Roms for your RN8PRO on that site
As for the way to flash them, order and everything, you will need to look for guides online,
I dont think any order matters, just make sure to flash them all before rebooting disconnecting device. But if you are unsure of what you are doing, you'd be probably best using a tool such as MiFlash.
5. Here you can find one from the MIUI community website guiding you through the use of MiFlash to flash a stock Rom on your device.
Just note you do not have to use any tools to flash the .images of all partitions, you can easily doing it from command line using fastboot flash command one after an other.
Also note that installing TWRP is usually not needed to flash stock Roms (unlike flashing custom roms). Trying to mess up with the recovery partition is actually what seem to brick most of the devices.
However please note UNLOCKING your BOOTLOADER is MENDATORY.
Hope this helps.
Regards,
Click to expand...
Click to collapse
Did you check if NFC works with Indonesian ROM?
maanni said:
doesnt matter if you switch to any rom variant .i have switched mine to indonesian ,europe and indian and alll worked fine execpt indian version felt a bit laggy .just download the fastboot version of the rom and flash it through mi flash tool xiaomiflash .your bootloader needs to be unlocked and dont forget to check cleann all button in mi flash and dont check clean and lock
Click to expand...
Click to collapse
yossidme said:
Muad.Dib,
Thanks for your detailed reply.
If I understand correctly, unlocking the bootloader voids the warranty just the same as rooting the phone, so if all I want is to get call recording, I may as well just root the phone and save the bother of flashing a different ROM.
Does that make sense to you, or do you see any advantage to flashing a different stock ROM instead of just rooting the phone? From past experience I've seen that rooting has additional benefits anyway.
BTW, I bought my phone on Banggood. It was advertised as Global ROM, and that appears to be what it has. As soon as I turned the phone on it updated to MIUI Global 11.0.2.1; I don't know what version it was before the update.
Click to expand...
Click to collapse
You're welcome, I am happy if I was useful to you in any kind of ways.
Well yes and no. Yes apparently you 'could' achieve call recording when rooted (yet I still fail doing so even if I installed the default MUI apps module I got from Telegram group. The setting to automatic recording is set to on yes, but I dont see recordings in the supposed destination folder nor I can see a simple button to record any voicecall I used to have on older versions of Android. Me failing to make it work - I did not try very hard to be honest - does not mean you cannot find someone who succeeded into doing so in that telegram group for RN8PRO).
That said it would not be a 'native' solution, just a patch/workaround. If it works well great, if not, well...
On an other hand by flashing to a Rom which does support it natively, well you are covered for the use you need.
So the advantage I see (with the included disadvantages) is better support for the function which is not supported for privacy reasons en Glob/EU market.
Does that come at a price?
Probably.
For example are you ready to trade off NFC for native call recording support? That may be a choice you have to make in the end. Again that said, if you root your phone on that new Rom, install NFC drivers manually as root (I see no reasons why that would not be possible after all) you may be able to patch NFC on that other Rom since unlike Indonesians market phone, you do have NFC hardware.
For example, myself, I wish I could have made that kind of bargain/trade off, giving up that NFC feature I have no need for, to get 8GB or Ram + 2x Sims + SD and not an hybrid tray. Unfortunately that's not the kind of trade I could make here in EU unless I would have ordered directly from Amazon.in (assuming that would have been possible) or third party website, but that was not possible for warranty reasons among other things.
Hope this helps.
Regards,
yossidme said:
Did you check if NFC works with Indonesian ROM?
Click to expand...
Click to collapse
Yes it does as it is officially available in every variant expect indian variant.
UPDATE:
I finally had the time to test the MIUI-default-apps Magisk module available for download on Telegram group, originally made for MIUI 11.0.1.0, and it works properly on MIUI 11.0.2.0 EEA. Does not require changing Rom.
Hope this helps.
Well, I have finally started the process, but got stymied by the Bootloader Unlock tool (Couldn't unlock. Please unlock 168 hours later.). Quite frustrating. I see that a lot of people have this problem and had to try again more than once, waiting a week between attempts.
Is there a workaround or do I just have to wait a week and hope for the best?
Also, assuming all goes well and I eventually manage to unlock the bootloader and flash the Indonesia ROM, do I use the same tool to re-lock the bootloader (in order to restore the security of the phone)?
And if I want to unlock again in the future, will I again possibly get the "wait and try again next week" message, or does that only happen the first time?
Thanks.
Muad.Dib said:
UPDATE:
I finally had the time to test the MIUI-default-apps Magisk module available for download on Telegram group, originally made for MIUI 11.0.1.0, and it works properly on MIUI 11.0.2.0 EEA. Does not require changing Rom.
Hope this helps.
Click to expand...
Click to collapse
yossidme said:
Well, I have finally started the process, but got stymied by the Bootloader Unlock tool (Couldn't unlock. Please unlock 168 hours later.). Quite frustrating. I see that a lot of people have this problem and had to try again more than once, waiting a week between attempts.
Is there a workaround or do I just have to wait a week and hope for the best?
Click to expand...
Click to collapse
No workaround, you just have to wait (and yes I know how freaking frustrating it was for me...). You can even start meditation classes meanwhile it helps
yossidme said:
Also, assuming all goes well and I eventually manage to unlock the bootloader and flash the Indonesia ROM, do I use the same tool to re-lock the bootloader (in order to restore the security of the phone)?
Click to expand...
Click to collapse
It depends on what your the flavor of the phone you got. You may want to have a look at that other thread Relock bootloader after flashing ROM Indonesia where we actually covered this exact subject
The good thing about that 7 days wait period is you can gather all the intel you need to be 100% ready when the time come to seriously mess up with things.
So you know, once your bootloader is unlocked, first thing you will want to do BEFORE anything else, is blow off that security which needed Auth Account to unbrick account (ONLY WORKS FOR PIE, ANDROID 9 MIUI VERSION BEWARE).
All information is here: [GUIDE][INFO][PSA] Redmi Note 8 Pro - Megathread
yossidme said:
And if I want to unlock again in the future, will I again possibly get the "wait and try again next week" message, or does that only happen the first time?
Thanks.
Click to expand...
Click to collapse
The waiting time is for one time only (THANKS GOD!).
So if you relock, beside having to get your hands on the unlock tool once again and have added the same infos as for the first time in the phone, you will be able to unlock right away.
That's at least a good news
Hope this helps,
Regards,
Muad.Dib said:
UPDATE:
I finally had the time to test the MIUI-default-apps Magisk module available for download on Telegram group, originally made for MIUI 11.0.1.0, and it works properly on MIUI 11.0.2.0 EEA. Does not require changing Rom.
Hope this helps.
Click to expand...
Click to collapse
My friend,
Would you like be so kind and share that magisk module with others or maybe just indicate the spot where I can get it? I would love to try this out. THX
kamyk70 said:
My friend,
Would you like be so kind and share that magisk module with others or maybe just indicate the spot where I can get it? I would love to try this out. THX
Click to expand...
Click to collapse
Yes of course.
It is a module you can find on the Telegram group called "Redmi Note 8 Pro | OFFICIAL".
Like me you will have to go in there even if you do not use Telegram.
Once there and you got the /notes it is called the default apps.
I cannot share it myself here because I am not the developer of that module, as you can understand that's against forums policies.
All I can tell you is it works correctly on EEA MIUI 11.0.2.0.
Good luck!
Hope this helps.
Muad.Dib said:
Yes of course.
It is a module you can find on the Telegram group called "Redmi Note 8 Pro | OFFICIAL".
Like me you will have to go in there even if you do not use Telegram.
Once there and you got the /notes it is called the default apps.
I cannot share it myself here because I am not the developer of that module, as you can understand that's against forums policies.
All I can tell you is it works correctly on EEA MIUI 11.0.2.0.
Good luck!
Hope this helps.
Click to expand...
Click to collapse
Thanks man, I got it! ?
I have disovered that there are different NGC protocols and that my Redmi Note 8 Pro does not read NFC cards of some protocols. I'm wondering if it might not be a driver issue. where would I look for NFC drivers?
Thanks
Muad.Dib said:
For example are you ready to trade off NFC for native call recording support? That may be a choice you have to make in the end. Again that said, if you root your phone on that new Rom, install NFC drivers manually as root (I see no reasons why that would not be possible after all) you may be able to patch NFC on that other Rom since unlike Indonesians market phone, you do have NFC hardware.
Regards,
Click to expand...
Click to collapse
kamyk70 said:
Thanks man, I got it!
Click to expand...
Click to collapse
You are much welcome, glad I could help
Regards
---------- Post added at 10:21 ---------- Previous post was at 10:20 ----------
yossidme said:
I have disovered that there are different NGC protocols and that my Redmi Note 8 Pro does not read NFC cards of some protocols. I'm wondering if it might not be a driver issue. where would I look for NFC drivers?
Thanks
Click to expand...
Click to collapse
Sadly I have no idea. I think you should make a new thread about this to get more visibility and probably more answers from people who actually knows the answer.
Hope this help.
Regards.
Muad.Dib said:
UPDATE:
I finally had the time to test the MIUI-default-apps Magisk module available for download on Telegram group, originally made for MIUI 11.0.1.0, and it works properly on MIUI 11.0.2.0 EEA. Does not require changing Rom.
Hope this helps.
Click to expand...
Click to collapse
Hi can you share more details???IS IT SAFE?? I want miui message and call apps not Google's one... How can i have them without changing ROM to Indonesian??? Now i have global ROM.
yossidme said:
Did you check if NFC works with Indonesian ROM?
Click to expand...
Click to collapse
yup it is working perfectly fine on indonesian rom as i am still using it
Alisoofi said:
Hi can you share more details???IS IT SAFE?? I want miui message and call apps not Google's one... How can i have them without changing ROM to Indonesian??? Now i have global ROM.
Click to expand...
Click to collapse
Hey,
Sorry was AFK for a while. In case you still need answer, going to reply just in case.
Well there is not much to add, you simply install the module from within Magisk once it installed, you reboot, and it works out of the box, you go in the settings and you set it as you like.
Good luck!
Do i need to root before installing it ?
Do i need to root before installing it ?
Follow and complain here.
Let ASUS know their bootloader implementation is VERY NOT FRIENDLY to us. I've been modding my Android devices since the Android 2 era and this is the first time I encountered an UNOFFICIALLY UNRECOVERABLE state which is a HORRIBLE experience.
Me? Have played with
Samsung(S5 to S9 and Tab/Odin is a good thing)
XiaomiRedmiPoco(Main device for me today, very modder friendly and robust)
Huawei(Remember when they allow applying for BL unlock?)
Apple(LOL jailbreak from A4 SoC until iPhone X(meantime Samsung S8 looks gorgeous) lost my interest)
And various small brands or exited market big brands(honorable mention Lenovo LePhone C101. My first smart device/Android and received big community support at the good old time)
ASUS. Fix your buggy BL. Fix your policy. Release everything we need to fix OUR DEVICES of OURSELVES. Just ONE step closer to perfect.
Just imagine how stupid is this:
Everytime you want to update you operating system, your UEFI/BIOS firmware might break.
And worse, that you don't have free official resources to fix it?
And can it be worse? Yes! Your Warranty is maybe void because you may unlocked bootloader, now supposedly only ASUS service center have the file to fix it.
Ha now it's interesting. That's the era of ANTITRUST. Even Apple won't do it(Worst case DFU, easily fixable using OFFICIAL iTunes).
WT*?
yeah dude i'm bricked up rn
Paid here, paid there.
Yeah sure.
Exploit people.
Perhaps instead of ranting about asus, you could tell us what you have done exactly to brick your device, and someone might be able to help you ? can you get into fastboot at all?
EDIT: quoted content removed.
Never use this firmware, because it has not been modified, 100% of fingerprints and IMEI will be lost after use. You need to modify the firmware before you can flash it.
mahdibassam said:
Perhaps instead of ranting about asus, you could tell us what you have done exactly to brick your device, and someone might be able to help you ? can you get into fastboot at all?
Click to expand...
Click to collapse
Trying to flash img unpacked from update zip. Which you should NOT do. Because Android 12 dynamic partition.
iMoc said:
Trying to flash img unpacked from update zip. Which you should NOT do. Because Android 12 dynamic partition.
Click to expand...
Click to collapse
Ok, yes you definitely should not do that
So just wondering, you went and grabbed some img files and made the decision to flash them, why is this any fault of asus?
mahdibassam said:
Ok, yes you definitely should not do that
So just wondering, you went and grabbed some img files and made the decision to flash them, why is this any fault of asus?
Click to expand...
Click to collapse
1\ The fastboot code in their bootloader have bugs, any CORRECT command you type can easily break bootloader then stuck you in 9008.
2\ The normal update method failed because THEIR UPDATER did do things wrong.
3\ They refuse to provide official ROM to let yourself fix it. SEND IT TO ME TO FIX IT, AND I MIGHT CHARGE YOU SOME.
....\
N\ You go talk to Apple about it because they are experts about saying YOU USED IT WRONG.
Anyone asked for help gets it for free so far.
All devs on my chat group agree at least fastboot flashable should be available on the official download page.
MOD EDIT: off topic content removed
Did you manage to unbrick your phone?
I managed to semi hard brick my phone. Can get into fastboot but unable to start recovery mode from fast boot and phone doesn't show up from adb devices.
I guess I'll start a new thread but any tips?
insideoft said:
Did you manage to unbrick your phone?
I managed to semi hard brick my phone. Can get into fastboot but unable to start recovery mode from fast boot and phone doesn't show up from adb devices.
I guess I'll start a new thread but any tips?
Click to expand...
Click to collapse
If you can boot into fastboot you can just flash the RAW ROM file available a few days ago. It's not bricked in this case.
Moderator Information
Hello everyone,
I have cleaned the thread from off topic contents and posts. Please focus on problem solving related discussion, not finger pointing or flaming each other. We all come here to solve the issues and learn some new stuffs.
Thanks.
iMoc said:
If you can boot into fastboot you can just flash the RAW ROM file available a few days ago. It's not bricked in this case.
Click to expand...
Click to collapse
Sorry long time ago since I was into this stuff previosly.
That fixed it, thanks for the help!
same here