Hi.
I have a problem with my Oneplus X smartphone.
I can't find a similar problem anywhere on the forum.
I've used the MSMdownloadtool 2.0 to recover from a brick. Can go into fastboot and oxygen os recovery but no matter what firmware I try to flash the phone won't boot into anything.
After the oneplus logo it just goes to a black screen and the notification led turns on.
When it is connected to a PC it shows up a 4 separate removable devices.
The bootloader is locked. I can't unlock it because I can't access developer settings because I'm not able to boot into anything.
Does anyone know how to fix this?
Thank you.
s3r3tin said:
Hi.
I have a problem with my Oneplus X smartphone.
I can't find a similar problem anywhere on the forum.
I've used the MSMdownloadtool 2.0 to recover from a brick. Can go into fastboot and oxygen os recovery but no matter what firmware I try to flash the phone won't boot into anything.
After the oneplus logo it just goes to a black screen and the notification led turns on.
When it is connected to a PC it shows up a 4 separate removable devices.
The bootloader is locked. I can't unlock it because I can't access developer settings because I'm not able to boot into anything.
Does anyone know how to fix this?
Thank you.
Click to expand...
Click to collapse
If you have recovery side load may help.or try full unbrick method rather than mini.
Fap4k said:
If you have recovery side load may help.or try full unbrick method rather than mini.
Click to expand...
Click to collapse
i did try that. didn't help either.
I used this guide and worked for me.....
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
i did too... didn't work. the Oneplus tech team tried the same thing. Didn't work.
s3r3tin said:
i did too... didn't work. the Oneplus tech team tried the same thing. Didn't work.
Click to expand...
Click to collapse
Same problem here. My device is now in the RMA process and I'm still waiting for their answer if they will repair it on warranty.
They told me that I have voided the warranty because the phone is bricked.
hello, here the same problem.... tried a few TWRP recovery versions but can't access the internal Storage. After the try to flash the phone with the MSMdownloadtool 2.0 (original OP Recovery Flash-Tool) the Oneplus X even boot anymore. No idea what happens with the newest Generation OPX
Date of Manufacture was November 2016?! Perhaps, the problem is the newer OOS 3.xxx. With OOS2.xxx i had no problems to Flash CM13 to a few OPX
Oneplus_X_Flasher said:
hello, here the same problem.... tried a few TWRP recovery versions but can't access the internal Storage. After the try to flash the phone with the MSMdownloadtool 2.0 (original OP Recovery Flash-Tool) the Oneplus X even boot anymore. No idea what happens with the newest Generation OPX
Date of Manufacture was November 2016?! Perhaps, the problem is the newer OOS 3.xxx. With OOS2.xxx i had no problems to Flash CM13 to a few OPX
Click to expand...
Click to collapse
Sorry but with your pseudo, it's a kind of funny
"tried a few TWRP recovery versions but can't access the internal Storage. " what do you mean by that?
Explain what happen at start. OS version, BL state....
Kéno40 said:
Sorry but with your pseudo, it's a kind of funny
"tried a few TWRP recovery versions but can't access the internal Storage. " what do you mean by that?
Explain what happen at start. OS version, BL state....
Click to expand...
Click to collapse
my normal "pseudo" was not available, so i take this funny one XD
Bootloader unlocked, OS --> OOS 3.x. Smartphone had boot into OS.
Recovery cant access internal Storage (Stock Recovery & TWRP)
After the stupid idea using the Oneplus original recovery tool the Smartphone cant boot anymore into the OS.
Now the Bootloader ist locked, cant open him anymore. Stock Recovery & TWRP cant access internal Storage.
OOS 2.x doesn't Boot. Android boot animation doesn't show.
So the main problem was, i want to flash CM13 but cant access the internal Storage (unable to mount data, system etc) wipe, formating, erasing was also not possible. even Fastboot had no access.
After using the "mega unbrick Quide" from Oneplus with the MSNdownload tool @ Qualcomm back door the Smartphone is "bricked"....Fastboot, recovery etc all good, but can't boot the OS (OOS2.x) Bootloader is locked, internal Flash still locked :silly::crying:
Fastboot command are OK?
Whatt's the output of "fastboot devices" &
"fastboot oem device-info"
If you have the old OOS 2 recovery on it, fastboot reflash the OOS recovery then try OOS 2.2.3 full rom zip
Old stuff links here : http://forum.xda-developers.com/showpost.php?p=69170103&postcount=45
If still a problem, and you think the BL is already on the new version, try to fastboot reflash TWRP 3.0.2.1 official and then OOS 3.1.4 with it.
To transfer it, use the microSD card.
After Flashing over the Qualcomm back door, the bootloader ist locked. so fastboot says of course, Bootloader ist locked (Fastboot oem device-info) that means, i cant flash anything by sideload or fastboot codes... and when i try it over the Recovery Boot, recovery is not able to mount /Data /System /cache and so on. so i am not able to flash anything XD Neither cm nor stock oxygen in the version OOS2.x / OOS3.x. I try the old bootloader, the new Bootloader and the TWRP 2.8.x, TWRP 3.0.2.0, TWRP 3.0.2.1, TWRP 3.0.2.2 and the Stock Recovery from CM and OnePlus
I've never had this behavior of a mobile phone The Technical Support Team of ONEPLUS even cant help. very strange. Here someone with the same strange problem... http://forum.xda-developers.com/oneplus-x/help/twrp-access-internal-storage-t3513748
The only way to flash anything to the phone is over the Qaulcomm BackDoor. With the new Bootloader & Kernel of OOS3 the boot animation of OOS3 starts and the phone gets hot. but not boot into the OS. And i can't find anywhere the system.img of OOS3. in the Recovery Tool from OnePlus ist the system.img from OOS2 (I have exchanged single items from directory xxx.img)
sorry it is very difficult to explain this complex problem in english XD
IT from Oneplus tried to flash OnePlus_15_A.11_160420 but it still didn't work. Bootlader is locked so TWRP is not an option or is flashing anything trough fastboot. Only Qualcomm Msmdownload tool or qfil. I've tried the old bootlader, new boolader, h2os, ColorOS, Miui ... but the phone just won't boot into any OS. it stays on a black screen with a white led on and that is it.
if the Qualcomm driver mount you a few partition under Windows, you can flash the internal Storage with an clone of a running OPX. I found an guide how to write direct into the Flash with a PC
Unfortunately I'm from a small town in Croatia. Here I think no one even knows what a Oneplus mobile phone is not to mention owning one... so I am out of luck.
UPDATE: I will get my repaired OPX (or a new one, don't know yet) back tomorrow. They repaired/exchanged it, I had the same problem, black screen and white led. Perhaps my good was to remove the "tampered"-flag from fastboot oem device-info
When I told them I use linux and don't have access to a windows PC they didn't even try the remote-session and told me to send it to them right away.
s3r3tin said:
Unfortunately I'm from a small town in Croatia. Here I think no one even knows what a Oneplus mobile phone is not to mention owning one... so I am out of luck.
Click to expand...
Click to collapse
i have access to two working Oneplus X but the dead phone did not show the removable drive under Windows so i thing we have to send the dead phone back to OP and hope the can fix oder replace it
You should remove the "tampered"-flag before you send it to them. It's simple:
Use the MSMdownloadtool 2.0 to flash twrp (just swap the recovery.img in the MSM-folder). Then you can start the recovery, but I could not do any swipes (screen didn't react), so I couldn't get past the first screen asking if I wanted to mount system r/o. But adb shell was working.
This I used to use the guide at http://forum.xda-developers.com/oneplus-x/help/guide-unlock-bootloader-oneplus-x-using-t3362640
Use adb push/pull to get the file to your pc.
After dd-ing the modified partition back, I used MSMdownloadtool 2.0 to flash the latest original oneplusX-recovery you can download at their site.
I told the support I never rooted the device and was acting like a complete noob, said I had no idea what android version I was on and it seems they accepted it.
It's definitely a hardware problem. Touch isn't working either. The IT guy checked the oem info himself after the flash and after boot was uncussesful and asked me if the phone was rooted. My warranty is now voided. I have decided to sell my oneplus x for parts.
Related
So, I've stupidly let my son try and flash a custom rom on his generic chinese tablet (Cambridge Sciences StarPAD 9 SE) and he found a few very similar spec tablet roms on the internet which said they require TWRP to be installed before flashing. So he's installed that, rebooted into recovery but the TWRP doesn't fit the screen in terms of resolution size. Now, that's not the main problem. The main problem is that the touch screen doesn't work at all within TWRP so I can't select any of the options. Whenever I power off the device and power it back up, it reboots to TWRP and doesn't boot to the main ROM. He said that it did originally reboot to the ROM whenever he first installed the TWRP because he said that it was the only way of getting to the recovery. So I thought that I could just use ADB and just force a reboot from there but off course, there is no ADB device driver to be found on the internet.. well not that I can find anyway.
I'll attach a photo for you guys and hopefully someone can help me with this as I've spent the best part of 2 days trying to figure out a fix but am now stuck.
I'm now able to access the device by adb however I don't know what to do from there.
Any help?
Does anyone have any firmware for this device? I can't find anything on the internet at all. If I could get a firmware img then the device will be fixed.
The build number from the firmware is: fiber_evb-eng 4.1.1 master 20130530
the command is "adb reboot" AFAIK
Did he take a nandroid backup before flashing? It looks like a version of twrp that is not compatible with the tablet was installed. Not every device supports touch screen recovery mode. Can you use the volume rocker to navigate?
I can almost guarantee you won't find the firmware for a Chinese tablet. I've just been trying to help someone in a similar situation but the best we could manage was a ROM that had lots of glitches.
Edit how did he flash TWRP if it was incorrectly flashed ie: fastboot flash boot recovery.img instead of fastboot flash recovery recovery.img then that may produce a device that would boot straight into TWRP. I've heard of that happening on a nexus 7
Sent from my C5303 using xda app-developers app
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Completely Bricked
Me too need a stock rom of ta 1056. Please help if you could manage to provide a helping hand... ?
I had the same issue like yours, looping in twrp. then i tried to flash it with a so called stock rom from net, guess what it went completely bricked and I donnow what to do. ??
mrabudi said:
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Click to expand...
Click to collapse
It's simple. just get the stock recovery (and boot, optional) to flash it with fastboot and go to recovery and wipe it and you'll be ok.
and also using the twrp on this phone is not a great idea to wipe.
if you wanna wipe. please use "fastboot -w" to wipe the phone while bootloader is unlocked. or stock recovery to wipe.
Because twrp built this recovery with only formatting option was ext4 to /data and /cache. So the phone cannot operate properly. Which leads to fake failed decryption notification.
Data partition must need to be formatted under f2fs format.
And finding rom for this phone is pretty easy. Just find some nb0 file for this phone (any variant of this phone should work) and extract it with "nb0 extractor" and then flash it with SP Flash tool by mediatek.
That's my way. I don't know how will you do. But normally you only need the nb0 file and then flash it with OST LA (Nokia's flash tool based off Intel's SUT L1/L3 tool).
My Nokia 1 TA-1047 stuck at Nokia logo screen
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
cuantonhonhoi said:
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
Click to expand...
Click to collapse
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047. Since it's a universal ROM so any variant of the phone can also work) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to look at line with partition "metadata" and then edit "boundary_check" to false.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
kutiz21 said:
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to hide/delete line with partition "metadata" in scatter.txt and you can flash it perfectly.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
Click to expand...
Click to collapse
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
pabloluih said:
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
Click to expand...
Click to collapse
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
kutiz21 said:
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
Click to expand...
Click to collapse
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
That's weird. If you unlocked the bootloader and install adb/fastboot (must be latest version. Older version will not recognize the phone, download platform-tools from google dev site, don't download adb tools off XDA) + Nokia's driver from emulated CD drive (every time you plug the phone to computer with official rom, you'll see it) properly then it should be able to work.
You need to check the fastboot device driver Device Manager (devmgmt.msc) and see if the driver is properly installed yet.
You can only use "fastboot -w" once the bootloader is unlocked. And booting up the phone. It will say the bootloader is in Orange state.
You need to unlock oem bootloader from developer settings when the stock rom is there. And in fastboot too
Here is how you unlock it:
Enable oem unlock from dev settings
Then reboot to fastboot mode (bootloader)
Do this:
"fastboot oem key "serial number string converted to md5, not imei strings" "
"fastboot oem unlock"
Volume up
Then you are actually unlocked the bootloader.
Unlock from developer settings only will not do the trick. It only allows you to have ability unlock the bootloader in fastboot.
If you stuck on the Encryption unsuccessful screen. Try wipe it with stock recovery or "fastboot -w" (if you properly unlocked the bootloader)
If you think you can't do anything anymore. Just flash the ROM provided you above.
If you need the extracted ROM for SP flash tool and the fastboot driver. I can link it to you.
Most of all drivers will automatically install off Windows Update if you're on Windows 10 (except the fastboot driver, and yes. SP flash tool drivers are also provided by Windows 10 too)
Also. You should update the phone to the latest software update when flashing stock rom too. Because newer builds for this phone is compatible-friendly with GSI rom (Treble ROMs like AOSP Android 9 or 8.1 by phhusson)
Updates on Android 9/10
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
Nokia might harden the security of the device so you can't use Magisk on stock rom.
I just bought a Nuu R1 Rugged Phone. It has Oreo 8.1.0 on it.
It is an "unlocked" phone. But I don't know if unlocked refers to the phone carrier or to the boot loader. (I'm thinking phone carrier.)
The last I rooted my tablets was Android 5, which required using a custom script that a dev here wrote that temporarily ran CW via fast boot.
I would like to root my R1. I hear now that Magisk is the way to go. (Instead of SU.)
Most every Guide says that I have to have TWRP installed before installing Magisk. But there's no TWRP for the R1. And I am incapable of compiling my own.
I learned, from Nuu Tech Support, that I can get into the phone's Recovery mode with some hidden button pushes. Here's a screen shot:
My first question is, could I simply install Magisk by selecting "Update from SD card"?
If it's not that easy, then, second: I can also get to a fastboot screen. (Not shown here.) Could I install Magisk from ADB on my computer?
I suppose a third question: Is there a version of TWRP that's compatible with this phone? And if so, how do I find it? It would be nice to have a Nandroid backup.
I am willing to show various screens that come up from various button pushes if that would help a dev here.
More data for TWRP'ing
So, I see that one needs an image of the OEM ROM to compile TWRP. I found two sites on the web that claim to have the ROM. (Before the R1 was officially released.) Sounds sketchy. Will try to get an image from Tech Support.
In the meantime, I found that the bootloader can be unlocked (or allowed to be unlocked) via a setting under Developer Options.
I contacted Nuu Mobile Support and they were kind to send me the MediaTek USB drivers for the R1.
It was a two step process to get the driver installed for ADB. But now I have access to the R1 via ADB.
I read here on the forums that I can boot TWRP via fastboot, and not risk ruining/corrupting the R1's Recovery Partition.
Anyone know of a TWRP model version that's close enough to work on the R1? (I presume a TWRP for another MediaTek device might work?)
I would hate to try KingRoot to get root.
I found a website called unofficialtwrp.com. It has a TWRP for the MediaTek 6739, running Oreo 8.1, with 16/2 GB. That's exactly what the Nuu Mobile R1 has.
So, hopeful that this would allow me to root my R1, I tried it. (Short version: Didn't work.)
I already had ADB installed and could talk to my R1 via ADB.
But once the R1 had booted into fastboot mode via ADB, I got a message from fastbood devices that it was "waiting."
I learned that that message means that I didn't have drivers for fastboot.
I ended up installing a fresh version of Win8.1 and using the Windows' updater to find the needed drivers. I had to have the R1 plugged in to the USB in fastboot mode for this to work. After that, I could talk to the device via the fastboot command.
So I unlocked the boot loader (which wiped my data - not every Guide warns you about that) and I did "fastboot boot recovery.img."
I got the message that the recovery file had transferred. After abotu 15 seconds, the phone rebooted. But no TWRP.
Rats.
I didn't want to try the fastboot flash command in case this unoffiical twrp from an unofficial site bricked my phone. If I understand things correctly, booting in fastboot to the recovery.img should give me a temporary instance of TWRP.
Presumably, after copying Magisk into memory, I would be able to get root that way.
PMikeP said:
I found a website called unofficialtwrp.com. It has a TWRP
Click to expand...
Click to collapse
Whoa you have been busy you must've heard XDA helps those who help themselves.. :highfive:
I just dropped by to say, 1st rule of modding is taking a pristine stock backup..
For MTK devices, there is a tool called SP Flash Tools, a quick search will help you take a full backup using this tool.
Afterward, you can even try using SP Flash Tools to flash a Magisk patched boot image to your device for ROOT!
Hope this helps!
Thanks. I did see SP Flash Tools mentioned and I did take a look at it. While I've rooted before, I'm trying to get my head around a Scatter File.
Everything I've read so far - well, almost everything - says that I need TWRP to get Magisk installed. But if you think it can be done via SP Flash Tools, I'll start playing with it.
Root nuu r1
Did u ever manage to figure out how to do this & get TWRP to install? :fingers-crossed:
No, I haven't had time to play with rooting lately. I still would like to root it tho.
Anyone know how to root the nuu phones?
someone has the boot.img i need the image
I will port TWRP for you in case you have stock recovery.img
jjgvv said:
I will port TWRP for you in case you have stock recovery.img
Click to expand...
Click to collapse
plis
do you have stock rom?
Didn't realize how common this was until I had to look around for a fix. Apparently when flashing a new rom (In this case it was Oxygen OS, Bliss, and Lineage I was trying) It's possible to screw up your Persist partition which govern your sensors. As a result me and a few other people when flashing new roms lose auto-rotate. So I was looking on ways to fix it, but the downloads were too old and broken.
So **** it, I decided to try flashing Miui global from the recovery tool.
So my system image, and recovery image are gone. That leaves me with just Fastboot with unlocked bootloader.
I explained my situation, but here's what I'm really asking. #1 I used to have a Xiaomi account that was authorized to unlock my bootloader. It's been over a year, but before the recovery tool bricked my Mi Pad, it said EDL not authorized. So do you lose your permissions over time? Anyway to get it back.
And #2, does anyone have, know, or would like to provide me backups to vendor, firmware, and/or persist so I can try to fix those? I don't have the time tonight, but even though I don't have a system or recovery, I'm assuming with an unlocked bootloader and fastbook, I can still flash twrp, and work my way from there...
Lastly #3, does anyone know how to bypass EDL not authorized in the recovery tool? This is my preferred way of recovery, since it would reflash all the partitions back to stock and I could just re-mod from there...
I have actually recovered from a destroyed system image, destroyed recovery image, with a locked bootloader. But didn't encounter the EDL issue in my memory, it's been so long I forgot how that happened
Just like to add that I discovered that I still have recovery access, so I could just flash a rom to get back into working order, but that still leaves my sensors not working. So if anyone has a link or backup for Persist partition that would be appreciated
Okay, I know no one replied or helped, but I resolved my own issue, and I'll describe how I messed myself up to get myself better.
1. Flashed a rom via TWRP, this somehow led to rotation not working. Learned rotation sensor data is in Persist partition. Assuming this partition overwritten, corrupted, or likely wiped due to negligence.
2. This led to me trying out Xiaomi recovery tool. I would find out that my account isn't authorized anymore. So flashing tool would always stop flashing when it came to flashing the kernel. Then I created this thread for help. Particularly to acquire a backup of someone's Persist. Help did not arrive
3. This led me to download the Chinese rom (flagship zip) of Miui for Xiaomi Mi Pad 4. This was going to overwrite my recovery and vendor partitions, so I was hoping it would flash my Persist partition as well.
4. System would not boot, softbrick/bootloop. Recovery reverted to stock Chinese. Bootloader still unlocked. Booted into Fastboot
5. ADB terminal, typed:
Code:
fastboot devices
Getting device ID, looking good. Then typed
Code:
fastboot flash recovery rec.img
(I renamed TWRP to rec.img for lazy reasons) ADB says writing flashed recovery successful.
I reboot into recovery. Recovery still Chinese stock ?️?️?
Back to Fastboot, repeat #5, same. Then I type
Code:
fastboot erase recovery
ADB confirms erased recovery, I type:
Code:
fastboot boot recovery
ADB does not detect recovery. So I'm thinking my recovery is gone now... Then I try booting into recovery through Vol Up + Power to make sure recovery had been destroyed... Recovery still Chinese stock ?️?️??
So my assumption was correct that I couldn't overwrite my recovery partition, and my fear was that I needed to enable USB debugging even though my system partition is destroyed
6. I boot back into Fastboot and I type
Code:
fastboot boot rec.img
This boots TWRP without flashing it to your recovery partition... Atleast this works.
7. Attempt to wipe System/Data/Cache/Internal, even though only half those weren't necessary. Could not wipe. Mounted, then repeated... Could not wipe. Assuming this was encryption related, I go back to Wipe and just Slide to format to factory conditions. Finally getting somewhere here.
8. Tired of this hole I dug myself into, I plug in my USB flash drive and flashed TWRP Permanently using TWRP, reboot into recovery to confirm -> looking good -> Flash Lineage + Gapps, with the acceptance that because I didn't have an authorized Xiaomi account anymore, and no one would share a Persist backup, that I was just gonna have to deal with no rotation and rely on an app-crutch
9. Boot into System, rotation working. ?️??️
I didn't think flashing the zippable Chinese rom would actually fix Persist. I originally intend to just use the Chinese Miui and setting up my Mi Pad 4 with my Xiaomi account to somehow re-authorize my account to try the flashing tool again. I did not expect the bootloop, and I damn sure didn't expect ADB telling me I successfully flashed recovery or erased it, only to find out stock recovery kept refusing to go away.
And my final question is:
Can anyone tell me how much usable storage the 32GB Mi Pad 4 should freaking have?!
I always used Micro SD flashed as Internal Storage so I'd always see 80GB free. But now on a fresh install on a new rom I see that I only have 22GB usable storage, on a 32GB device, Lineage less than 1GB, and gapps only 200MB. So all together OS should not exceed 2-3GB unpacked...
WHERE THE HELL IS THE REST OF MY STORAGE?!
I SHOULD HAVE 5 MORE GB, I SHOULD HAVE 26~27GB OF USABLE STORAGE BUT MY SYSTEM SAYS ONLY 22Gb
DOES anyone else have 10GB of storage missing?!
How much should I have?!
Thanks this is good read and may help someone in the future.
There is a persist.zip shared in the Miui 12 port thread.
I have the 64gb version but never took notice of how much remaining storage out of the box. Next time I flash a ROM I'll check and let you know.
scloss84 said:
Thanks this is good read and may help someone in the future.
There is a persist.zip shared in the Miui 12 port thread.
I have the 64gb version but never took notice of how much remaining storage out of the box. Next time I flash a ROM I'll check and let you know.
Click to expand...
Click to collapse
Yeah, I found persist zips but the link was broken.
This is actually the 2nd time I bricked my device, but the 1st time I bricked it, I had just got it around the same time I got the Poco F1, so I had a Xiaomi account, with authorization. So I assumed how I un-bricked my device the 1st time, would fix the brick the 2nd time. I never imagined my account would lose authorization. So flashing the Miui using the Xiaomi recovery tool was useless. So I had to learn/relearn other tricks.
I actually enjoy bricking my devices a little bit for the experience to learn new things. Like this time, I didn't know you could run a recovery on the side through fastboot commands without flashing it. I also didn't know that recovery partition would reject flashes because mi stock recovery was encrypted (or maybe it was a USB debugging thing) , I didn't know Mi Flash authorization could be revoked, and I didn't know what the Persist partition did.
My 1st brick happened because of the Mi recovery tool. No one told me that if you buy a Mi Pad 4 with unlocked bootloader from AliExpress, use the Mi recovery tool, the tool actually intentionally bricks your device and locks your bootloader. The fix for that was opening the mi pad up, shorting some contacts, force the pad into EDL mode, and use a patched bat file and run the tool again and pray it takes. Because I wasn't authorized it wouldn't run the tool.
Thank ****ing God my bootloader was still unlocked this time. I don't think I could have came back
Post 225 in the Miui 12 port thread, the persist.zip is still being shared I checked just now. Not that you really need it if flashing the full rom got your rotation back.
There was 1 time my twrp touch screen became unresponsive after flashing and trying different twrps, and then system touch screen also gone dead, so I can't restore persist even if I wanted to.
One question, lots of tutorials talk about extracting the persist.zip from the fastboot ROM, but I can't find it in the fastboot rom... But the MiFlash tool had never failed me so anything goes wrong I'll just MiFlash it.
Hi,
My favourite phone is the Xiaomi Redmi note 3 Pro SE with Lineage OS 13 (Yes marshmallow).
I got a new one that was in endless bootloop and I planned to get it working.
I don't know if the bootloader has been unlocked and how (last time I checked it was written locked), if a custom ROM as been flashed or anything that could been done on it before I get it.
After many tries I first succeed to install LineageOs 13 on it, what I remember:
I go to fastboot mode
I go to edl mode
I flashed it with an old MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_global_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. (This is the way to get a recovery with no need to unlock bootloader)
I started it directly to TWRP recovery mode (to be sure TWRP will stay it I guess?) changed the language and checked OTA checkbox in parameters
I started this old official ROM once (to get the full storage capacity)
I discovered it was a 16GB ROM / 2GB RAM version instead a 32GBROM / 3GB RAM I previously knowed
I restarted to TWRP recovery mode
I wiped david/cache
I flashed the last knowed LineageOS 13 for this phone: https://forum.xda-developers.com/re...ageos-13-0-t3533744/post83687823#post83687823
I wiped david/cache
I flashed the last radeon kerned on it
I wiped david/cache
I restarted it to LineageOS 13
I restarted to TWRP recovery mode, changed the language and checked OTA checkbox in parameters
I flashed magisk (sytemless)
I wiped david/cache
I restarted it to LineageOS 13
I could use it install a lot of things, was happy with it
Before succeeding I tried a lot of combinations of official ROM/TWRP/MiFlash versions and this couple was the only one working.
Other MiFlash versions don't detect the phone in edl mode
But 2 weeks later, just after installing a new app, the phone sudently reboots and I got stuck in bootloop again...
I could go to recovery one time, I selected reboot system, now I can't go to recovery anymore
I still can go to fastboot mode and edl mode, and I can flash a ROM, but whatever I flash I can't go away from bootloop.
What could the new bootloop come from?
Is my installation sequence good?
Why only this combination of official ROM/TWRP/MiFlash versions was working?
Why can't I start a ROM anymore after a new flash?
Why can't I go to the recovery anymore after a new flash?
How to check if the emmc memory is defective (I got no error while flashing)?
Thanks for reading, hope someone still cares on this old great phone
Sorry for my bad English
No clue what the problem may be. What app did you install? You could always try to go back to stock if you haven't already. Basically wipe phone completely and flash stock through mi flash.
JD. A said:
No clue what the problem may be. What app did you install? You could always try to go back to stock if you haven't already. Basically wipe phone completely and flash stock through mi flash.
Click to expand...
Click to collapse
Thanks for your answer.
The last app before bootloop was a sms/mms backup app on google store I get through Aurora.
I tried to flash the stock ROM (old one) kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 but it doesn't start, always bootloop.
I have no option to wipe on the only miflash version that detect my phone in edl : the 2016.04.01.0 64 bit version. so I choose flash all data/storage include, but still bootloop.
Why are you using such a old rom? Use latest miflash and latest global. On the bottom right of miflash you should have something like clean and lock. Just note that if you're unofficially unlocked you'll need to apply for unlock or unlock unofficially again.
JD. A said:
Why are you using such a old rom? Use latest miflash and latest global. On the bottom right of miflash you should have something like clean and lock. Just note that if you're unofficially unlocked you'll need to apply for unlock or unlock unofficially again.
Click to expand...
Click to collapse
Other Miflash version don't detect my phone when it is in edl mode
I could start other stock rom, I know tried this ones:
kate_global_images_7.6.8_20170608.0000.00_6.0_global_2040bd5a39
kate_global_images_8.12.13_20181213.0000.00_6.0_global_304fc0692b
But I couldn't flash my LineageOS 13 + recovery with those.
I tried so much combinations TWRP/Stock rom, I don't remember what I tested.
I just know the MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. was the only one combination that worked for me for installing LineageOS 13 + recovery working
Now, every time I try to flash something (whatever it is) it goes to bootloop...
Only fastboot and edl mode are working
If you have other links / combinations I would be happy to try
ROUGE13 said:
Other Miflash version don't detect my phone when it is in edl mode
I could start other stock rom, I know tried this ones:
kate_global_images_7.6.8_20170608.0000.00_6.0_global_2040bd5a39
kate_global_images_8.12.13_20181213.0000.00_6.0_global_304fc0692b
But I couldn't flash my LineageOS 13 + recovery with those.
I tried so much combinations TWRP/Stock rom, I don't remember what I tested.
I just know the MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. was the only one combination that worked for me for installing LineageOS 13 + recovery working
Now, every time I try to flash something (whatever it is) it goes to bootloop...
Only fastboot and edl mode are working
If you have other links / combinations I would be happy to try
Click to expand...
Click to collapse
This is a little bit to late to the party but the latest both dev rom and global works for me with the latest me miflash. No problems what so ever. Seems like you're facing a hardware issue.
JD. A said:
This is a little bit to late to the party but the latest both dev rom and global works for me with the latest me miflash. No problems what so ever. Seems like you're facing a hardware issue.
Click to expand...
Click to collapse
Hi,
No, not too late my phone is still waiting, so thanks for your answer
Could you tell me witch version of rom / tool did you use?
I will try on a other windows computer to be sure there is no conflict with old tools I installed before.
If it works I will flash CM13 (marshmallow), I thought I should not use a too recent dev/global ROM before flashing CM13, but I don't remember were I read this. Is this true?
ROUGE13 said:
Hi,
No, not too late my phone is still waiting, so thanks for your answer
Could you tell me witch version of rom / tool did you use?
I will try on a other windows computer to be sure there is no conflict with old tools I installed before.
If it works I will flash CM13 (marshmallow), I thought I should not use a too recent dev/global ROM before flashing CM13, but I don't remember were I read this. Is this true?
Click to expand...
Click to collapse
I'm not home this weekend so I can't say for sure. gismoZ recommends using the 8.0.2 firmware or something like that can't remember, but the latest works just fine on my kate. The latest miflash is from 20200314 and just get the latest global rom and try to flash it.
I tried with an other windows computer, I successfully used last MiFlash version
But now, whatever I flash, ROM version or recovery version, it stay in bootloop when I power it.
I expect the eMMC memory to be faulty but why doesn't I have any error while flashing?
How to be sure this comes from the eMMC chip?
Some people have successfully changed it on the mediatek version of the phone:
https://fr-fr.facebook.com/16816505...c-kmvtu-done/1821360108117225/?_fb_noscript=1
https://translate.google.com/transl.../03/service-hp-xiaomi-redmi-mi-note-mati.html
If I go on this solution I have some questions before:
Must the eMMC chip be programmed before soldering it?
If not, can I program it with MiFlash once soldered?
If not, have I to use some special touch/contact on the mainboard to program it?
How to be sure of the chip model to buy?
Will the chip come already balled? Or have I to ball it before soldering it on mainboard?
Could I buy a 32GB chip instead 16GB original one?
Something else to test before going on this crazy last chance solution?
I bought a EDL flash cable, but I think I don't need it on this phone, I alway success to go to EDL mode from fastboot mode with a small batch script.
Hello ,
Any chance I could get an answer anymore or is my problem too specific maybe?