Related
My LYF LS-4503 mobile stuck logo problem. boot animation worked but . not load the android os.
i have lyf ls-5002, and as far as i can help, try rebooting in recovery and then wipe data/factory reset.
it should work. if not, then we'll see for some other solution
ajith13 said:
My LYF LS-4503 mobile stuck logo problem. boot animation worked but . not load the android os.
Click to expand...
Click to collapse
Universal unbrick guide:
Terminology - types of bricks:
Soft brick - often occurs in the shape of a bootloop or any other problems with booting such as always getting to recovery or not getting past the carrier logo. This type of a brick, which shows some signs of life, can in most cases be fixed.
Hard brick - As the name implies, your phone can essentially used as a brick and it shows no signs of life. This kind of a brick is rare and in theory should be unfixable. However there are advanced methods of fixing your phones such as JTAG, but they require extra tools and accessories.
The decision:
Is my phone soft or hard bricked?
If you answer yes to all of the questions below you probably have a hard birck:
Test as said in order!
Nothing happenes when you hold or press the power button
You cannot get the screen to even turn on by pressing or holding any combination of buttons on your phone
Nothing happenes if you do the same as about but with your phone plugged into a charger
Nothing happenes when you plug your phone into a computer
When you plug in your phone into a computer it does not recognize it as a phone, storage or any other media device
Nothing happenes when you try all of the above again, but with removing the battery in between steps for 10 seconds and putting it back in again
Nothing happenes when you try all of the above again, but after leaving the phone plugged into a charger for 2 hours
If all of the questions are a "yes", then you either have a broken charging port and and a discharged battery or you have a hard brick.
The unbricking:
There are many methods of unbricking and they are all different to each phone. Here I will list the most common methods that often succeed.
Samsung users skip to 4. method.
1. If you have access to a stock recovery:
Method 1:
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Choose “Wipe Cache Partition”.
5. Choose “Wipe Data / Factory Reset” to delete all your settings and apps, using the correct ROM.
6. Reboot your device.
Method 2:
Download the stock rom for your phone. It should be in ".zip" format. Make sure it's the official version
(Find it by Googling something like "[your phone model] stock rom")
Put the file on your phone's external SD card.
Make sure that the rom is for your exact phone model.
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Select "apply update from external storage"
5. Navigate to the zip file you copied to your phone
6. Install it.
If you get Status Error 7 that means you didn't download an official stock rom.
2. If you have access to a custom recovery:
Method 1:
Try stock recovery method 1
Method 2:
1. Find a stable custom rom for your phone or if you want to download the stock rom
Make sure that the rom is for your exact phone model.
2.. Copy the zip file to the phone's external SD.
3. Install the zip
(If you have a custom recovery you probably know the drill)
3. If you have access to fastboot mode:
First install ADB and fastboot drivers (if you haven't already):
To install it on windows there is a handy tool called the 15 Second ADB installer which will install pretty much everything you need.
On Ubuntu install with:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
On Fedora:
Code:
sudo dnf install android-tools
On OS X using Homebrew:
Code:
brew install android-platform-tools
Once you have the drivers installed you have to find a recovery image for your phone to install a custom recovery.
You can try one of the popular recoveries such as CWM or TWRP.
You need to get the recoveryNameHere.img file for your phone.
Find it by Googling:
"[your phone model] TWRP recovery"
or
"[your phone model] CWM recovery"
Make sure that the recovery is for your exact phone model.
Now on your phone enter fastboot mode:
Turn your phone off.
You can try different button combinations. For my phone it's holding power and volume down buttons.
Once you're in fastboot mode plug your phone into a computer and open your terminal/cmd.
Type in:
Code:
fastboot devices
You should see a list of devices. There should be only one device ID number.
If you see the ID it's working. If you don't you didn't install the Google USB driver properly (on Windows) and if it says "'fastboot' is not a recognized command" or "No command 'fastboot' found" then you didn't even install your drivers.
If you have problems with installing Google "how to install adb and fastboot drivers"
Now that you know fastboot is working type in:
Code:
fastboot flash recovery C:\Path\To\Recovery.img
Replace "C:\Path\To\Recovery.img" with an actuall path of the recovery file you downloaded.
It should say success.
If it doesn't try to execute:
Code:
fastboot oem unlock
This will delete all data you had on your phone (games, game progress, apps...).
Now try
Code:
fastboot flash recovery C:\Path\To\Recovery.img
again.
Once you're done type in:
Code:
fastboot reboot
And your phone should still not work. Now what you have to do it try the custom recovery method above (number 2.)
4. If you have a Samsung device:
Try this tutorial of unbricking with Odin: click here
i cant take out my battery
Go into recovery mode. Choose Wipe cache/delvik. Then reboot. If that doesn't work you're going to have to go in recovery and factory reset
Lg k3 ls450
Hola buenas tengo un problema, mi LG enciende pero en la pantalla a cada rato aparece un mensaje diciendo que el ui del sistema se detuvo y así consecutivamente, ya intente hacer hard reset pero me aparece un mensaje de que el espacio de almacenamiento es insuficiente, así que. como podría solucionarlo, pensé en volver a instalar el firmware pero no encuentro kdz, o el LGUP .dll podrían ayudarme.
por favor
mod edit - translation added according to Forum Rules
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature).
Click to expand...
Click to collapse
-=-=-
Hello, I have a problem, my LG turns on but on the screen every time a message appears saying that the system ui stopped and so on, I tried hard reset but I get a message that the storage space is insufficient, so. as I could solve it, I thought about reinstalling the firmware but I can not find kdz, or the LGUP .dll could help me.
please
-=-=- @DeyvidRo
Greetings!
I've created a guide and composed a pack for ZTE Nubia 17 mini to unlock bootloader and install TWRP recovery then grant root access.
https://drive.google.com/folderview?id=0B-JUT41_C1ExLXJtUC1ZSXVldnM
It can be also used for Z17 (not mini) with some minor modifications.
Happy 'hacking' ! :fingers-crossed:
EDIT: Reports arrived on 'bootloader locked' screen not showing. Reports also came on successful process - after error encountered by the script - by continuing the steps of the guide.
OperatorB said:
Greetings!
I've created a guide and composed a pack for ZTE Nubia 17 mini to unlock bootloader and install TWRP recovery then grant root access.
https://drive.google.com/folderview?id=0B-JUT41_C1ExLXJtUC1ZSXVldnM
It can be also used for Z17 (not mini) with some minor modifications.
Happy 'hacking' ! :fingers-crossed:
Click to expand...
Click to collapse
for 6G+64G version of z17mini (snapdragon 653), consider revising the batch file as below before execute
fastboot oem nubia_unlock NUBIA_HX569H
it works perfectly on mine, thanks
unixwise said:
for 6G+64G version of z17mini (snapdragon 653), consider revising the batch file as below before execute
fastboot oem nubia_unlock NUBIA_HX569H
it works perfectly on mine, thanks
Click to expand...
Click to collapse
I'm happy for your success!
Yes you are abolutely correct. You need to edit the file according to your phone's model number.
unixwise said:
for 6G+64G version of z17mini (snapdragon 653), consider revising the batch file as below before execute
fastboot oem nubia_unlock NUBIA_HX569H
it works perfectly on mine, thanks
Click to expand...
Click to collapse
unixwise here is a link with rom updates if u are interested.
http://ui.nubia.cn/rom/detail/38
Hey, this tools with work since global 2.01 ROM ?
jordandroid64 said:
Hey, this tools with work since global 2.01 ROM ?
Click to expand...
Click to collapse
Yes, actually i made that guide after flashing with 2.01 ROM and it worked.
How could we flash new stock ROM, once custom recovery installed ?
Custom recovery does not effect the system that way. You will be able to install official updates as before.
Custom recovery just gives you more possibilities(root, unroot, install zip packs like gapps, backup, restore etc.)
Cool huh? :cyclops:
On my old phones that was not the case x) and if I flash RR, How could I flash stock ROM ?
jordandroid64 said:
On my old phones that was not the case x) and if I flash RR, How could I flash stock ROM ?
Click to expand...
Click to collapse
Well if you have backed up the system before RR then with restore (with twrp for example). If you don't have backup, your other option is to get the stock ROM.zip from somewhere then you install it with custom recovery. These are my thoughts.
OperatorB said:
Well if you have backed up the system before RR then with restore (with twrp for example). If you don't have backup, your other option is to get the stock ROM.zip from somewhere then you install it with custom recovery. These are my thoughts.
Click to expand...
Click to collapse
If no stock android 7 will come to Z17 mini in August then i will install RR or Mokee's and try restore stock to test it is working in practice. :victory:
jordandroid64 said:
On my old phones that was not the case x) and if I flash RR, How could I flash stock ROM ?
Click to expand...
Click to collapse
Well I've taken a look at RR then on Mokee's ROM then i tried to recover my backup of stock ROM and it did not worked out. It stucked at Nubia powered by android screen.
So the next trial would be to install the stock ROM.zip provided by the manufacturer.
I stay with Mokee's for now.
UPDATE: stock ROMs from Nubia official (v2.06) can be easily flashed with custom recovery if you dislike RR or Mokee's. However my TWRP had been uninstalled after flashing stock ROM. Though I could reinstall TWRP with the same method as first time.
--- Attendo il dispositivo...
Accertati che i driver siano installati
e che il telefono sia connesso con debug attivo
--- Il telefono sta per entrare in fastboot
--- Attendo il dispositivo
***************************************************************************************
The system cannot find the file specified.
* *
* reinstalla i driver presenti nella cartella *
***************************************************************************************
Sblocco il bootloader...
< waiting for device >
...
FAILED (remote: unknown command)
finished. total time: 0.009s
Press any key to continue . . .
and after retry " --- Attendo il dispositivo...
Accertati che i driver siano installati
e che il telefono sia connesso con debug attivo
"
avro.bd said:
--- Attendo il dispositivo...
Accertati che i driver siano installati
e che il telefono sia connesso con debug attivo
Gettting it when press 1 then hit enter ("Sblocco bootloader")
Click to expand...
Click to collapse
It means:
Waiting for the device...
Make sure drivers are installed
and that your phone is connected with active debugging.
Solution #1: install driver if you did not installed
Solution #2: enable ADB and OEM in developer options
Solution #3: use data cable (not only charger)
Check those above, i hope you succeed! :good:
Edit: Script is for device NX569J . In other case you need to edit it. For edit use readme_guide file.
OperatorB said:
Well I've taken a look at RR then on Mokee's ROM then i tried to recover my backup of stock ROM and it did not worked out. It stucked at Nubia powered by android screen.
So the next trial would be to install the stock ROM.zip provided by the manufacturer.
I stay with Mokee's for now.
UPDATE: stock ROMs from Nubia official (v2.06) can be easily flashed with custom recovery if you dislike RR or Mokee's. However my TWRP had been uninstalled after flashing stock ROM. Though I could reinstall TWRP with the same method as first time.
Click to expand...
Click to collapse
Did you flash stock ROM from updater or from twrp? Or flashing with other method
ndroe said:
Did you flash stock ROM from updater or from twrp? Or flashing with other method
Click to expand...
Click to collapse
With TWRP.
OperatorB said:
Greetings!
I've created a guide and composed a pack for ZTE Nubia 17 mini to unlock bootloader and install TWRP recovery then grant root access.
https://drive.google.com/folderview?id=0B-JUT41_C1ExLXJtUC1ZSXVldnM
It can be also used for Z17 (not mini) with some minor modifications.
Happy 'hacking' ! :fingers-crossed:
Click to expand...
Click to collapse
Hey! I tried this after running GizFlasher. I hit 1 and enter. The phone enters fastboot but it gives options such as 1. Reboot system now 2. Go into recovery 3. nubia emergency recovery 4. reboot to eload mode 5. power down. I am unsure what to do in this place. Please help. thanks.
verifiedthug said:
Hey! I tried this after running GizFlasher. I hit 1 and enter. The phone enters fastboot but it gives options such as 1. Reboot system now 2. Go into recovery 3. nubia emergency recovery 4. reboot to eload mode 5. power down. I am unsure what to do in this place. Please help. thanks.
Click to expand...
Click to collapse
After the phone boots into Fastboot mode you should see some text saying like 'device status: unlocked' . After that leave the phone alone and go back to the computer's command line terminal.
Then press a key to see the menu again (if you are not there). Then press "2 - Flash TWRP da fastboot". It will start to install TWRP on android.
Now you just wait until the phone opens TWRP when it finished installing.
Finally you can exit from terminal by "X" exit or press "0" then hit enter in menu.
I hope you succeed! :cyclops:
OperatorB said:
After the phone boots into Fastboot mode you should see some text saying like 'device status: unlocked' . After that leave the phone alone and go back to the computer's command line terminal.
Then press a key to see the menu again (if you are not there). Then press "2 - Flash TWRP da fastboot". It will start to install TWRP on android.
Now you just wait until the phone opens TWRP when it finished installing.
Finally you can exit from terminal by "X" exit or press "0" then hit enter in menu.
I hope you succeed! :cyclops:
Click to expand...
Click to collapse
Hi, I think u didn't understand. My phone shows a menu once I press 1 and enter.
--- Attendo il dispositivo...
Accertati che i driver siano installati
e che il telefono sia connesso con debug attivo
--- Il telefono sta per entrare in fastboot
--- Attendo il dispositivo
***************************************************************************************
The system cannot find the file specified.
* *
* reinstalla i driver presenti nella cartella *
***************************************************************************************
Sblocco il bootloader...
< waiting for device >
...
FAILED (remote: unknown command)
finished. total time: 3.283s
Press any key to continue . . .
this is the error
pls do let me know.
thanks,
verifiedthug said:
Hi, I think u didn't understand. My phone shows a menu once I press 1 and enter.
--- Attendo il dispositivo...
Accertati che i driver siano installati
e che il telefono sia connesso con debug attivo
--- Il telefono sta per entrare in fastboot
--- Attendo il dispositivo
***************************************************************************************
The system cannot find the file specified.
* *
* reinstalla i driver presenti nella cartella *
***************************************************************************************
Sblocco il bootloader...
< waiting for device >
...
FAILED (remote: unknown command)
finished. total time: 3.283s
Press any key to continue . . .
this is the error
pls do let me know.
thanks,
Click to expand...
Click to collapse
All right! The only problem seems to be that the pc does not see the phone.
For troubleshooting you may first check the drivers on your computer. Secondly make sure that "USB debugging" and "Enable OEM unlock" are turned on in the phone. Finally check the script file for spelling mistakes if you have edited it.
Write how did it go!
Hello everyone,
Please devs if you can move this thread to LG section,thanks
I need to flash patched boot image from magisk to this phone,but the problem is i cannot enter into fastboot mode and to unlock bootloader either.
Need some advices.
Cheers.
How i patch the boot image? I recently unlocked the OEM, this means that the bootloader has been unlocked, right?
ImTheHackerman said:
How i patch the boot image? I recently unlocked the OEM, this means that the bootloader has been unlocked, right?
Click to expand...
Click to collapse
ImTheHackerman said:
How i patch the boot image? I recently unlocked the OEM, this means that the bootloader has been unlocked, right?
Click to expand...
Click to collapse
yes
Hey guys, I have a k41s that I dawngrade to Android 9, and I can go into recovery (default) I was surprised = at the possibility of fleshing files via SD Card aply update, but I don't have any knowledge, I think that should be an easy one for you haha, if you can indicate some flesheavel file to save the whole population of k41s android 9  obd
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
guys forgive me, if the translator is a little bad. i'm with k41s i've rooted with the xda tutorial here, and i divulge this method, through two channels on yt and telegran. as there is no twrp for this model, I'm trying to install GSI roms, s the photos I post here are from the phh leneage OS, they install but even though the smartphone was formatted before it gets stuck in the password screen, I got these photos, unlocking , temporarily the frp by a technical assistance box program, we can only make modifications through mtkclient with celualr in BROWN mode, there is no adb fastboot, to start the android, if anyone can help me, please, if you have developers to manufacture twrp, my group and I are here to test, smartphone model k41s LM-K410 bmw, android 10 mtk 6765 arm32-binder64 vndk A/B,,
[email protected] said:
no we don't know how to flash files. zip on mtk client only img files
Click to expand...
Click to collapse
adm
could someone put this post on the list of the k41s? please
for all the controls the celualr disconnected and pressed the keys before by pressing the cable,
I do not know if you guys so able to read, I learned a lot from this forum, and everything I learned, helped me install this rom, and I'm using the translator, if you want to edit and fix, feel free..
phh rom gsi android 12,
stock rom 9 was already with root,
I clean op_a product_a and system_a, with the command;
py mtk e op_a,product_a,system_a enter .
on k41 has no fasboot I used BROWN mode with the mtkclient folder
removes the cable and leaves it off, the second command:
py mtk w vbmeta_a,system_a vbmeta.img.empty,leneapp.img
for all commands, six knows that the command already has to ta running on cmd, and after preciingvolume - and Google acistente with the celualr off, puts the cable..
after the second command, the cmd will load up to 100 and go back to the mtkclient folder, restart celualr do not enter format data or format by ae if not the loop.
will reboot and go to a password screen.
miss the password several times and the system will format and restart, when restarting does not take long, it will already eata on the home screen, without needing to configure the start.
wifi, connections all working videos on yt ok, to record audio it's buggy,
it will restart a few times after it has started, more later for kk
see root tutorial for k41s
because for the cmd to work it needs
of phyton3
and from the mtkclient folder.
[email protected] said:
clean first with command
py mtk and op_a,system_a,product_a enter
if yours is a, a, if it's b, b
and install the rom on the system_a partition
py mtk w vbmeta_a,system_a a space vbmeta.img.empty,leneapp.img
the commas for vbmeta and system and a space to indicate the img, rename the rom to leneapp to make it easier for me kk
the rom is on the arm32-binder64google apps architecture
Click to expand...
Click to collapse
if same know how to instal, twrp pleasse post
I cant belive. I was find how enter in fastboot to install 12 and e found this!!
[email protected] said:
adm
could someone put this post on the list of the k41s? please
for all the controls the celualr disconnected and pressed the keys before by pressing the cable,
I do not know if you guys so able to read, I learned a lot from this forum, and everything I learned, helped me install this rom, and I'm using the translator, if you want to edit and fix, feel free..
phh rom gsi android 12,
stock rom 9 was already with root,
I clean op_a product_a and system_a, with the command;
py mtk e op_a,product_a,system_a enter .
on k41 has no fasboot I used BROWN mode with the mtkclient folder
removes the cable and leaves it off, the second command:
py mtk w vbmeta_a,system_a vbmeta.img.empty,leneapp.img
for all commands, six knows that the command already has to ta running on cmd, and after preciingvolume - and Google acistente with the celualr off, puts the cable..
after the second command, the cmd will load up to 100 and go back to the mtkclient folder, restart celualr do not enter format data or format by ae if not the loop.
will reboot and go to a password screen.
miss the password several times and the system will format and restart, when restarting does not take long, it will already eata on the home screen, without needing to configure the start.
wifi, connections all working videos on yt ok, to record audio it's buggy,
it will restart a few times after it has started, more later for kk
see root tutorial for k41s
because for the cmd to work it needs
of phyton3
and from the mtkclient folder.View attachment 5494871
Click to expand...
Click to collapse
App banks works on this rom?
And thank you very much for this amazing work
[email protected] said:
py mtk w vbmeta_a,system_a vbmeta.img.empty,leneapp.img
Click to expand...
Click to collapse
Where is the vbmeta.img? Ir is a blank file?
Predro said:
Where is the vbmeta.img? Ir is a blank file?
Click to expand...
Click to collapse
inside the folder, mtkclient, it has a vbmeta.img file by default
Hi, any twrp for lg k41s?
Androi100 said:
yes
Click to expand...
Click to collapse
I've another phone with same problem, but bootloader isn't unlocked even doing the same thing. I cannot flash nothing because phone fastboot is disabled and from edl it check signature so is unuseful even if bootloader is unlocked, is like is locked.
Another thing, you can use some tools to develop twrp like philz auto recovery porter or twrp auto recovery porter by hovatek
Hello everyone! i managed to make a twrp for the lg k41s android 10 p22 arm32-binder 64, model bmw. I downloaded version 3.5 of twrp tipalia. I followed a tutorial here on the forum. I merged and edited the boot_a files, used fstab.recovery, unevent, among others. I installed the new twrp on the boot_a partition, it didn't boot into systema, it just rebooted when asked, and it went back to twrp. I edited the data and system paths, something like this, dev/block/platform/bootdevice/by-name/system and then system_a. I'm lost kkkkk if anyone can point me to solutions.
this is the file of the qui twrp did. i installed it by mtkclinte in BROWN mode.
kkkk I used the magisk zip, an aik-mobile kitchen, to open the boot. if I knew a way, to edit the twrp and by along with the boot files, I believe it would not be a problem to start the partitions, if that is the error.
Predro said:
Where is the vbmeta.img? Ir is a blank file?
Click to expand...
Click to collapse
in the foulder mtkclient. is one arquive of the folder. Kkkk
Skorpion96 said:
I've another phone with same problem, but bootloader isn't unlocked even doing the same thing. I cannot flash nothing because phone fastboot is disabled and from edl it check signature so is unuseful even if bootloader is unlocked, is like is locked.
Another thing, you can use some tools to develop twrp like philz auto recovery porter or twrp auto recovery porter by hovatek
Click to expand...
Click to collapse
but to use the hovatek tool, it requires you to have the recovery file, and the k12 up to k61 has no recovery partition to pull.
I managed to port the twrp by editing the boot of the k41s, but the systema does not start, ppr that the practically the twrp is on the boot partition
because I have no recovery partition, would have how I merge the twrp in boot, so that the boot could start the partitions?
já que eu não tenho ajuda dos gringos, pra querer escrever em outra língua .
Eu consegui fazer, um twrp, um cwm, e por último, o recovery da leneage bootar no k41s. o k41s melhor, a linha k12 ao k61 não possui recovery. eu consegui inatalar o cwm eo recovery da lineage editando o arquivo boot, o cwm depois de limpar a data, não inicia no systema, so reinicia em recovery. o twrp a mesma coisa. depois que é formatado a data pelo twrp, o sistema pede uma nova formatação pelo próprio sistema, e essa formatação do systema limpa a instalação do twrp. como se fosse preciso um arquivo de criptografia pro twrp. vamos ver o que essa recuperação diz depois do wipe. Mas de qualquer maneira, não da pra fazer muita coisa com ele, não tem opção de instalar zip, a nao ser pelo sidloade quebrado.
Mod translation via GT:
since I don't have any help from the gringos, to want to write in another language .
I managed to do, a twrp, a cwm, and finally, the recovery of the leneage bootar in the k41s. the k41s is better, the k12 to k61 line has no recovery. I managed to inatatar the cwm and the recovery of the lineage by editing the boot file, the cwm after clearing the data, does not start in the system, only restarts in recovery. the twrp the same thing. after the date is formatted by twrp, the system asks for a new formatting by the system itself, and this formatting of the system cleans the installation of twrp. as if you need an encryption file for twrp. let's see what this recovery says after the wipe. But anyway, you can't do much with it, there's no option to install zip, except for the broken sidloade.
I need root on my Cubot Note 20, but I can't figure it out
1) This guide soft-bricks my device: https://www.ayudaroot.com/root/rootear-cubot-note-20/ (so don't follow this tutorial if you are a Cubot Note 20 owner !!!)
2) At least there's a decent unbrick guide officially from CUBOT: https://cubot.net/platform/Support/detail/id/406/cid/30.html
3) Then I tried patching the boot.img with Magisk and flashing it with SP_Flash_Tool (like in step 2 - just with the boot.img file replaced) --> but that gives some signature failiure on boot --> bootloop again
So now my device is unbricked for the second time But I really need OTG and it's only possible to enable it when I'm rooted...... Can someone please help me?
I am to dumb to figure out how to post a new thread on here. However after much research, trial and error I have discovered how to root this properly!!!
WARNING after root. DO NOT RESTART PHONE UNTIL YOU RENAME "recovery-from-boot.p" FOUND UNDER /SYSTEM
***CUBOT NOTE 20 PRO***
Enable Developer Options In Android 10
Head over to the Settings app of your device via the notification shade or app drawer.
Scroll down and tap on ‘About phone.’
Find an entry labeled ‘Build number.’ Keep on tapping until you see a prompt that says ‘You are now a developer!’. You will be prompted to enter your device’s unlock code (PIN/Pattern/Password) at this point
Next go to Settings -> System -> Advanced -> Developer Options
Tap the slider on "OEM Unlocking" and "Enable USB Debugging"
Extract the attached file
Install MTKdriver.exe
plug phone into computer. Windows SHOULD install drivers for adb automatically
run file "flash - root.bat"
you are rooted.
***ANY CUBOT PHONE***
Follow directions provided by Magisk to root boot.img
Cubots has a BOOT.IMG VERIFICATION IMAGE!!!! .........
Flash the boot image with fastboot as directed
download "vbmeta(root).img"
put in folder with fastboot
run code - fastboot flash vbmeta vbmeta(root).img
**********DO NOT BLAME ME FOR FAILURE USE AT YOUR OWN RISK************
gosh please someone help me i did the instructions and my phone is bricked how can i fix it?
ConverterDreamer said:
gosh please someone help me i did the instructions and my phone is bricked how can i fix it?
Click to expand...
Click to collapse
thank God it works again xd and its rooted now
Owners of Cubot Note 20 Pro: does your phone support dual frequency (L5/E5) GPS?
Can be verified with this opensource app: https://play.google.com/store/apps/details?id=com.android.gpstest
Text L5 or E5 in "CF" column means dual freq is supported.
We need a new thread started on this phone with topics such as rooting and custom Roms.Not only does it come with a removable battery but it has a huge battery and ram.We desperately need some experienced developers to look help out.
Hey guys!
I finally managed to root my brand new Cubot Note 20 not with Magisk Manager but with adb + fastboot downloaded from this link: https://www.getdroidtips.com/flash-...all_the_Patched_Boot_Image_on_MediaTek_device.
Extracting the boot.img and reinserting this same patched.img sorry for the bad explanation, it's just to give an orientation. Extracting the boot.img and reinserting this same patched.img sorry for the bad explanation,.Now Titanium is already running on my terminal and removing the Gapps. Happy!
jediroadkilk said:
I am to dumb to figure out how to post a new thread on here. However after much research, trial and error I have discovered how to root this properly!!!
WARNING after root. DO NOT RESTART PHONE UNTIL YOU RENAME "recovery-from-boot.p" FOUND UNDER /SYSTEM
***CUBOT NOTE 20 PRO***
Enable Developer Options In Android 10
Head over to the Settings app of your device via the notification shade or app drawer.
Scroll down and tap on ‘About phone.’
Find an entry labeled ‘Build number.’ Keep on tapping until you see a prompt that says ‘You are now a developer!’. You will be prompted to enter your device’s unlock code (PIN/Pattern/Password) at this point
Next go to Settings -> System -> Advanced -> Developer Options
Tap the slider on "OEM Unlocking" and "Enable USB Debugging"
Extract the attached file
Install MTKdriver.exe
plug phone into computer. Windows SHOULD install drivers for adb automatically
run file "flash - root.bat"
you are rooted.
***ANY CUBOT PHONE***
Follow directions provided by Magisk to root boot.img
Cubots has a BOOT.IMG VERIFICATION IMAGE!!!! .........
Flash the boot image with fastboot as directed
download "vbmeta(root).img"
put in folder with fastboot
run code - fastboot flash vbmeta vbmeta(root).img
**********DO NOT BLAME ME FOR FAILURE USE AT YOUR OWN RISK************
Click to expand...
Click to collapse
Gulpiyuri said:
Hey guys!
I finally managed to root my brand new Cubot Note 20 not with Magisk Manager but with adb + fastboot downloaded from this link: https://www.getdroidtips.com/flash-...all_the_Patched_Boot_Image_on_MediaTek_device.
Extracting the boot.img and reinserting this same patched.img sorry for the bad explanation, it's just to give an orientation. Extracting the boot.img and reinserting this same patched.img sorry for the bad explanation,.Now Titanium is already running on my terminal and removing the Gapps. Happy!
Click to expand...
Click to collapse
Need help in finding a working recovery for the Cubot Note 20 Pro. After root I tried flashing the Twrp version 3.4.0-by nemo-nemo and it just stays on the TWRP splash screen. Ive also tried other TWRP versions and recovery's like orange fox but with no luck. I was hoping that someone with more expertise could help in some way.
elimoviebuff said:
Abbiamo bisogno di un nuovo thread avviato su questo telefono con argomenti come rooting e ROM personalizzate. Non solo viene fornito con una batteria rimovibile, ma ha una batteria e un'enorme RAM. Abbiamo un disperato bisogno di alcuni sviluppatori esperti che cercano aiuto.
Click to expand...
Click to collapse
Qualcuno può aiutarmi con la connessione hotspot con cubot 20 note pro ? La uso per connettermi con il mio PC e ogni volta vedo che ci sono utenti sconosciuti connessi alla mia rete . In questo telefono non vi è modo di vedere chi sia , né di impostare il numero di utenti max connessi. Ho cercato di reperire notizie ovunque, persino all'assistenza (inesistente) del produttore. Helppppp!!
Hi there, i have an huawei mediapad x2 701L with android 5.0.1, EMUI 3.0.5 and Build Number C199B003.
My device's battery drains fast and factory reset and even replacing it with a new battery couldnt solve it. Maybe flashing a new ROM (android 6 or newer versions) be able to solve the battery issues.
can you guide me to do that? i failed to get a BootLoader Unlocker code becuase of Huawei's new policies.
ps: i cant use credit cards for few months to use paid methods.
Can anyone help?
Unlocking BootLoader :
Requirements:
1. Huawei Mediapad X2 ( not region specific).
2. Minimal ADB Tools.
3. Four Credits in DcUnlocker website. (Costs mere 4 euro).
4. DcUnlocker Software
5. Backup of your personal data.
Procedure.
1. First you need to enable usb debugging setting. Connect the tablet to PC in file transfer mode, navigate to Settings -> System -> About Tablet, tap build number multiple times till you get message "You are a developer now" . Now navigate back to System, you will see developer options setting in the menu. Enable "usb debugging" and OEM unlock options in developer options.
2. Download the minimal adb tools zip (link above) and install it your pc.
3. Connect your tablet to pc with usb debugging enabled and open command prompt in the adb folder ( Shift Right click ). In the Command prompt window type
Code:
adb devices
and you will see a device connected in the output. Then type
Code:
adb reboot bootloader
, your device gets rebooted into fastboot mode and you will see message "Bootloader Locked". ( Don't close the command prompt window yet).
4. To Unlock BootLoader you have to go to DcUnlocker website (link above Step 3). There select New user account and your username any then your email and in credits click on " how much do I need " and select third option " Force Huawei Android bootloader unlock (old method) " you will be charged 4 euros. (IMPORTANT: note down to password after creating account)
5a. After successfully creating account download the Dc Unlocker Software ( Step 4) and install it in your PC.
5b. Open the dialer on your phone and enter *#*#2846579#*#* select “Background settings”, “USB ports settings”, “Manufacture mode”.
6. Open Dc Unlocker Software and connect the tablet in fastboot mode to the pc.
On the left side menu
Select Manufacturer -> Huawei Phones
Select Model -> Auto detect
and click on the search icon your device will be dectected in fastboot mode.
7. Click on Server on the right side menu enter your username and password and click on Check login, you will see your username and credits in the output window below.
8. Now click on the Read bootloader code (Unlocking -> Read bootloader code) in the right side menu and wait for the code in the output window. Once you get the Bootloader code note it down.
9. Now open the switch back to command prompt window in your pc, type
Code:
fastboot oem unlock your-unlock-code.
You will be prompted to select Yes/No in the tablet to unlock bootloader, select yes using volume buttons.
10. You have succesfully Unlocked your bootloader, your device gets factory resetted automatically and reboots.
amir774 said:
Hi there, i have an huawei mediapad x2 701L with android 5.0.1, EMUI 3.0.5 and Build Number C199B003.
My device's battery drains fast and factory reset and even replacing it with a new battery couldnt solve it. Maybe flashing a new ROM (android 6 or newer versions) be able to solve the battery issues.
can you guide me to do that? i failed to get a BootLoader Unlocker code becuase of Huawei's new policies.
ps: i cant use credit cards for few months to use paid methods.
Click to expand...
Click to collapse
bootloader unlock is not mandatory, but helps if somthing goes wrong.
I suggest you ton install Android 6 on your device, then install TWRP recovery next to stock recovey:
Huawei Mediapad X2 - Tutoriels
forum-frandroid-com.translate.goog
then install one of these 3 custom roms : Kangvip Slim B230, B207 Simply International, Unofficial LineageOS 13 by ajsmsg78
Huawei Mediapad X2 - Développement, ROM & Co
forum-frandroid-com.translate.goog
Everything is explained and sourced in links above
Djiban said:
bootloader unlock is not mandatory, but helps if somthing goes wrong.
I suggest you ton install Android 6 on your device, then install TWRP recovery next to stock recovey:
Huawei Mediapad X2 - Tutoriels
forum-frandroid-com.translate.goog
then install one of these 3 custom roms : Kangvip Slim B230, B207 Simply International, Unofficial LineageOS 13 by ajsmsg78
Huawei Mediapad X2 - Développement, ROM & Co
forum-frandroid-com.translate.goog
Everything is explained and sourced in links above
Click to expand...
Click to collapse
thx. i downloaded the B203, extracted it into my SD card and did the dload method 1 ) The simplest... but i faced error "Software install failed!" what should i do?
amir774 said:
thx. i downloaded the B203, extracted it into my SD card and did the dload method 1 ) The simplest... but i faced error "Software install failed!" what should i do?
Click to expand...
Click to collapse
1) did you check what's inside the file you did doncload, and follow this:
Comment installer une ROM officielle Huawei
Une fois que vous avez trouver un nouvelle rom pour votre X2 (voir l'épinglé sur où/comment les trouver), il vous faut l'installer. Je vous proposes 3 méthodes fonctionnent pour installer des roms Huawei: utiliser l'app android ou le programme windows Huawei Firmware Finder (voir milieu de post),...
forum-frandroid-com.translate.goog
for B203, the dload folder must be put at the root of a FAT formated SD card (or also at the root of internal storage, never tested it)
2) Try with B205 that I'm upoloading now to https://1drv.ms/u/s!AoChLp8DMXIsw0RCOljX3Jz7Zj_E?e=tBJ4hO, and again check what is in the downloaded material, and follow https://forum-frandroid-com.transla..._sl=fr&_x_tr_tl=en&_x_tr_hl=fr&_x_tr_pto=wapp
for B205, rename the zip file into update.zip, and place it in the dload folder described above.
let me know, but reading all https://forum-frandroid-com.transla..._sl=fr&_x_tr_tl=en&_x_tr_hl=fr&_x_tr_pto=wapp guaranty your success.
Djiban said:
1) did you check what's inside the file you did doncload, and follow this:
Comment installer une ROM officielle Huawei
Une fois que vous avez trouver un nouvelle rom pour votre X2 (voir l'épinglé sur où/comment les trouver), il vous faut l'installer. Je vous proposes 3 méthodes fonctionnent pour installer des roms Huawei: utiliser l'app android ou le programme windows Huawei Firmware Finder (voir milieu de post),...
forum-frandroid-com.translate.goog
for B203, the dload folder must be put at the root of a FAT formated SD card (or also at the root of internal storage, never tested it)
2) Try with B205 that I'm upoloading now to https://1drv.ms/u/s!AoChLp8DMXIsw0RCOljX3Jz7Zj_E?e=tBJ4hO, and again check what is in the downloaded material, and follow https://forum-frandroid-com.transla..._sl=fr&_x_tr_tl=en&_x_tr_hl=fr&_x_tr_pto=wapp
for B205, rename the zip file into update.zip, and place it in the dload folder described above.
let me know, but reading all https://forum-frandroid-com.transla..._sl=fr&_x_tr_tl=en&_x_tr_hl=fr&_x_tr_pto=wapp guaranty your success.
Click to expand...
Click to collapse
1) yes i did check it sir!
2) i faced the same error with B205. thanks for uploading it again.
is it necessary to root the device before installing a new android version or ROM?
Probably i do something wrong, but idk whats that.
ps: I did root the phone but it doesn't make any difference.
amir774 said:
1) yes i did check it sir!
2) i faced the same error with B205. thanks for uploading it again.
is it necessary to root the device before installing a new android version or ROM?
Probably i do something wrong, but idk whats that.
ps: I did root the phone but it doesn't make any difference.
Click to expand...
Click to collapse
1) If you carefully follow tutorial (root of sd card, good folder, packed or unpacked file), it should work, nobody had issue yet
2) no need to root for stock rom.
retry with B205, rename the zip file into update.zip, and place it in the dload folder at the root of your SD card. If failed at the root of intrnal storage. then:
- restart it by forcing the update (start by keeping the three buttons power, Vol+ , Vol- pressed) if .
or
- launch the installation from the hidden "project" menu (to access it, dial *#*#2846579#*#* as if to make a call)
but it seems you ara reaching the installtion routine , seeing your error message
if you root, it means you unlock your bootloader ?
amir774 said:
1) yes i did check it sir!
2) i faced the same error with B205. thanks for uploading it again.
is it necessary to root the device before installing a new android version or ROM?
Probably i do something wrong, but idk whats that.
ps: I did root the phone but it doesn't make any difference.
Click to expand...
Click to collapse
your solution might be here !