Related
i got a chinese version of razr v(xt885) and now it simply cant boot (always stuck in the M picture) so i need to flash it
here i got several questions that not quite sure of
1. i already got it rooted using a batch file through adb but i find it unable to receive official ota update, so how can i just flash it to the factory state, i mean i want everything the same when i bought it. yes i got a official zip file, but what should i do to totally reset the phone? just get into the boot mode and connect the RSDlite and reflash it?
2. i want to flash the australian retail rom to use Google servicećwill there be any problem in the process?
3. i did some study on how to flash it using RSDlite. in many instructions people suggest you need to double wipe your phone. so why and when you need to do this?
4. since you cant remove the battery in xt885 so if you just stuck in the M logo when booting i will stay there untill battery worn up so will it be a problem while flashing?
i m a absolute newbie so any help will be appreciated! good day!
Wrong forum.
You are not your iPhone 5
#tylerdurden
I have a Nokia XL RM-1030 v1.2.3.1. Im currently using the stock OS of this phone but rooted it with Nokia X Manager. I have a problem installing Gapps on this phone because everytime I try installing it by RootExplorerApp+Reboot or by downloading NokiaXGapps Zip and installing it via NokiaXManager it wont install. First I downloaded a NokiaXGapps zip then used the RootExplorerApp+Reboot method and in the guide that i followed it clearly said that after i reboot it PlayStore along with other Gapps will be installed but after i reboot my phone it didnt showed up in menu. Thinking for another way ,I tried using NokiaXManager to install it so i downloaded the required zip and when im going to flash it it FAILED . It said something like this "Skipping md5..md5 file not found. Error flashing this zip" .Sorry i cant clearly remember what it said but Im quite sure that it said something like that. Any help or advice is greatly appreciated! Thanks!
(P.S. I really feel the need to move my CoC account in this phone! And also sorry for my bad english )
Please note that you will need to register to ask this question and get support. When you have done so you may post your question here
Good luck
I've been using Gnabo v_7 version for quite a long time, and a very simple and beautiful day when I woke up my Samsung GT-N8000 was stuck on bootscreen. I wasn't able to do much so I got this "Brazil stock rom" that I found in a website, and it flashed all right, except for the detail that there is something at the screen that I haven't got a bloody clue how to remove. hahaha
And still, whenever I try to install another room, I got stuck at bootlogo and so on. I'm kinda lost here, mind a little help?
I traveled around the forum but well, I'm a little dumb so I couldn't find any proper information about, how to solve this. I would like to know if there is a way to remove this thing from the main screen, and post here the image for you guys to see it please.
I tried to post the image here to make it easier understanding, but since I got this login recently I can't =\
Thanks
Install custom recovery (if you haven't already. If you already have it installed, make sure to update to latest version), root device, wipe everything and flash custom ROM.
DroidTwe4kz said:
Install custom recovery (if you haven't already. If you already have it installed, make sure to update to latest version), root device, wipe everything and flash custom ROM.
Click to expand...
Click to collapse
So far I've tried the rom = N8000XXUDNE4 [still bootloop], then another 4.1 android version of other German rom XXALGA and nothing. Downloaded 3 Brazilian versions, and nothing. [I am from Brazil]. The only one that worked flashing using Odin was one called "KIES_HOME_N8000UBALGA_N8000ZTOALG3_N8000UBLG5.tar". And still, not recognizing my cellphone chip, and with some big watermark at the middle of the screen showing some information about the ROM and the version is 4.0. Even though this one worked fine, I was able to root and when I tried to flash another room, BANG! Bootloop again! =\
I was looking at the forum topics and I read some about ADB or something like that can fix this and "break" this bootloop making the device work normally again with the roms. But i haven't got a clue how to use it. Please help me! =\
vitortakeda said:
So far I've tried the rom = N8000XXUDNE4 [still bootloop], then another 4.1 android version of other German rom XXALGA and nothing. Downloaded 3 Brazilian versions, and nothing. [I am from Brazil]. The only one that worked flashing using Odin was one called "KIES_HOME_N8000UBALGA_N8000ZTOALG3_N8000UBLG5.tar". And still, not recognizing my cellphone chip, and with some big watermark at the middle of the screen showing some information about the ROM and the version is 4.0. Even though this one worked fine, I was able to root and when I tried to flash another room, BANG! Bootloop again! =\
I was looking at the forum topics and I read some about ADB or something like that can fix this and "break" this bootloop making the device work normally again with the roms. But i haven't got a clue how to use it. Please help me! =\
Click to expand...
Click to collapse
You can use ADB to push/pull files to Android. I don't know if you can use it to fix bootloop. With it, you can also reboot to recovery and sideload zip
DroidTwe4kz said:
You can use ADB to push/pull files to Android. I don't know if you can use it to fix bootloop. With it, you can also reboot to recovery and sideload zip
Click to expand...
Click to collapse
Well, after 2 days of research and paying attention on things here, I found out that my problem is "/EFS error". Meaning to use ADB to recover or fix it? But I don't know how to use this. I've downloaded 3GB of it but I was lost about using, and uninstalled. Is is there any short or better version and some good tutorial about using to retrieve my EFS so I can install another roms? I'm using original stock rom now, Brazilian android 4.0 and that's the only only the device is working fine but of course missing things as my cellphone card and the yellow message at the top of the screen. Please guide me through ADB.
P.s Is there a way to create /efs or something like so the device work properly? Cause I've deleted when I installed some rom, and I have no backup here. =\
Thanks!
vitortakeda said:
Well, after 2 days of research and paying attention on things here, I found out that my problem is "/EFS error". Meaning to use ADB to recover or fix it? But I don't know how to use this. I've downloaded 3GB of it but I was lost about using, and uninstalled. Is is there any short or better version and some good tutorial about using to retrieve my EFS so I can install another roms? I'm using original stock rom now, Brazilian android 4.0 and that's the only only the device is working fine but of course missing things as my cellphone card and the yellow message at the top of the screen. Please guide me through ADB.
P.s Is there a way to create /efs or something like so the device work properly? Cause I've deleted when I installed some rom, and I have no backup here. =\
Thanks!
Click to expand...
Click to collapse
Here is tutorial about how to install ADB and Fastboot drivers and use them. Unfortunately, I don't know how to use it to restore efs. Sorry.
Hello everyone, I hope I'm writing in the right section.
I'll go straight to the issue: after finally deciding to install a custom rom on my device (HUAWEI GX8), i decided to opt for this one: https://forum.xda-developers.com/moto-g4-plus/development/rom-aospextended-rom-v3-0-t3537792
The first problem i had to face was the "ERROR:7" (so the rom seemed to be made for a different phone than mine) that occured while installing the rom in the twrp, but being that the rom was specifically made for my phone I followed this guide: https://www.youtube.com/watch?v=wed03948gcg and fixed the issue, resulting in a perfect installation... or so I thought.
After rebooting, the phone didn't start the os but was stuck in the twrp (I tried rebooting multiple times and in different ways of course).
Being that I had made a backup before installing the new rom, I decided to restore that backup from the twrp... but still the phone is stuck in the twrp and I don't know what to do :crying:
I hope somebody can help me because I'm starting to panicking.
Cheers in advance.
PS: I'm a complete newb so this was the first time I installed a custom rom, I tried searching for this problem online but couldn't find a solution that fitted me. I hope I won't ask too many stupid questions.
SlimeAndroid said:
Hello everyone, I hope I'm writing in the right section.
I'll go straight to the issue: after finally deciding to install a custom rom on my device (HUAWEI GX8), i decided to opt for this one: https://forum.xda-developers.com/moto-g4-plus/development/rom-aospextended-rom-v3-0-t3537792
The first problem i had to face was the "ERROR:7" (so the rom seemed to be made for a different phone than mine) that occured while installing the rom in the twrp, but being that the rom was specifically made for my phone I followed this guide: https://www.youtube.com/watch?v=wed03948gcg and fixed the issue, resulting in a perfect installation... or so I thought.
After rebooting, the phone didn't start the os but was stuck in the twrp (I tried rebooting multiple times and in different ways of course).
Being that I had made a backup before installing the new rom, I decided to restore that backup from the twrp... but still the phone is stuck in the twrp and I don't know what to do :crying:
I hope somebody can help me because I'm starting to panicking.
Cheers in advance.
PS: I'm a complete newb so this was the first time I installed a custom rom, I tried searching for this problem online but couldn't find a solution that fitted me. I hope I won't ask too many stupid questions.
Click to expand...
Click to collapse
The ROM that you flashed was NOT made specifically for your device, you have HUAWEI GX8, the ROM was made for Moto G4 Plus. You would have know this if you had looked at the forum it was posted in. It was posted in in the Moto G4 forum, not in a Huawei forum.
The "fix" that you used didn't help.it successfully flash, it only help you "force" the ROM to flash. You bypassed a safety measure that was designed to keep you from flashing the wrong thing, now you're dealing with the results of forcing it to flash on a device it wasn't meant for.
Learn to pay attention to what you are reading.
You need to flash your stock firmware to fix this.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
The ROM that you flashed was NOT made specifically for your device, you have HUAWEI GX8, the ROM was made for Moto G4 Plus. You would have know this if you had looked at the forum it was posted in. It was posted in in the Moto G4 forum, not in a Huawei forum.
Learn to pay attention to what you are reading.
You need to flash your stock firmware to fix this.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I'm sorry I may have linked the wrong page, either way on the website of the rom I downloaded the right thing, I'm sure about it because I checked it multiple times (the error I made in writing the post may be cause by me panicking, sorry :crying: ).
While waiting for answers I installed a different twrp and it WORKS! I'm so happy I could cry. Thank you nonetheless for your help (Still dunno what the problem was though xD)
@SlimeAndroid as you installed ROM of different phone, it might not get installed as ROM zip contains script for Mobile verification.
I assume you had wiped /system and after installation of wrong ROM you rebooted your phone without reading if TWRP said you don't have any OS installed or what. (That means you have ran without any OS, that may be reason why you stuck with TWRP.)
But after Restoring Backup of Working ROM, it should boot your device, but it doesn't.
We (on G4 plus) have faced issue: when phone start, it always goes to TWRP/recovery instead of booting to system.
Are you facing similar ?
Solution for this problem was to clear bootloader data, by using fastboot commands (i assume you know how to do, otherwise ask for better explanation )
Run this two commands from Comand Prompt
-> fastboot oem fb_mode_set
-> fastboot oem fb_mode_clear
This worked for us. You can try, if doesn't work then flash Stock ROM.
____Mdd said:
@SlimeAndroid as you installed ROM of different phone, it might not get installed as ROM zip contains script for Mobile verification.
I assume you had wiped /system and after installation of wrong ROM you rebooted your phone without reading if TWRP said you don't have any OS installed or what. (That means you have ran without any OS, that may be reason why you stuck with TWRP.)
But after Restoring Backup of Working ROM, it should boot your device, but it doesn't.
We (on G4 plus) have faced issue: when phone start, it always goes to TWRP/recovery instead of booting to system.
Are you facing similar ?
Solution for this problem was to clear bootloader data, by using fastboot commands (i assume you know how to do, otherwise ask for better explanation )
Run this two commands from Comand Prompt
-> fastboot oem fb_mode_set
-> fastboot oem fb_mode_clear
This worked for us. You can try, if doesn't work then flash Stock ROM.
Click to expand...
Click to collapse
If you read the post above yours, you'll see they solved the issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
You always have to make sure the download is for your model of phone(settings -about) and always make sure the download has properly downloaded and I use md5 checksum as this verifies the download is not courupt.
Sent from my iPhone using Tapatalk
I was trying to root my phone but i failed, doing so many wrong steps,now my samsung a7 is bricked, i cant charge it and i cant power it on, i also tried connecting it to a pc but the pc cant recognize it, any advice please to fix this? I really dont know what should i do now, thank you so much guys.
Can you talk us through the steps you did.
Is usb debugging enabled?
You may be able to use the samsung flashing software to recover but if you missed 1 or maybe 2 steps and have now wiped the device fully then you need to RMA. No os then no proof of your actions for a warranty claim to be rejected
enter download mode and flash firmware from Odin3
aIecxs said:
enter download mode and flash firmware from Odin3
Click to expand...
Click to collapse
Pretty much spot on, If all else fails then RMA
FKX1997 said:
Can you talk us through the steps you did.
Is usb debugging enabled?
You may be able to use the samsung flashing software to recover but if you missed 1 or maybe 2 steps and have now wiped the device fully then you need to RMA. No os then no proof of your actions for a warranty claim to be rejected
Click to expand...
Click to collapse
Im really sorry but i was actually not hard bricked, i thought i was hard bricked and i eventually got it turned on, so here is the whole story, i was about to root my phone and i watched a tutorial on how to but for some reason i trusted myself and didnt watch the video so i got into this situation, i enable USB debugging and OEM unlock( it deletes all of my files like a factory reset) i didnt know that i have to paste the magisk and the magisk apk to my phone and i flashed the bootloader thing from the tutorial i watched and then after that i decided to watch the tutorial and to my surprise the tutorial paste the magisk, so i panicked, i dont know what to do and i thought i was stucked at the downloading process so i decided to search more while panicking and i found that tenoshare Reiboot and Ult has this feature that will exit you to the downloading and now i tried them both but it failed, and i panicked more because now my phone just wont stop bootlooping so i just decided to drain its battery because its built in, i also tried flashing twrp but it cause me more panicking because it kind of glitches more so good thing i tried to go to downloading again by connecting to a pc and it worked, and the good thing is that the file i downloaded has a recovery flashable thing so i flashed it again, i escaped the teamwin bootloop and now i tried researching more causing me to figure it and i think i need to download the firmware again, but here is my biggest problem, i dont know the original place of the phone(i only know the country because its like a phone given only to me) i also dont know what is the original patch security of my phone( idk if its safe to just download the latest of the firmware) thank you for any advice
FKX1997 said:
Pretty much spot on, If all else fails then RMA
Click to expand...
Click to collapse
What is RMA? Please help me
Hi, i just wanna know if flashing the orginal firmware of a samsung phone, is it important to know the original patch security and the region(i know the country)? Thank you for all advice
Yatsuko said:
Hi, i just wanna know if flashing the orginal firmware of a samsung phone, is it important to know the original patch security and the region(i know the country)? Thank you for all advice
Click to expand...
Click to collapse
All you need is the correct firmware for your specific model number for your specific region/carrier and the firmware must have a binary that is equal to or higher than the binary of your currently installed firmware. The binary is indicated by the 5th character from the right in the firmware build number. Find that character in the build number of your currently installed firmware and compare it to the same character in the build number of the firmware that you want to flash. If the binary of the firmware that you want to flash is equal to or higher than the binary of your currently installed firmware then you can safely flash it, if the binary is lower than the binary of your currently installed firmware, you will not be able to flash the firmware that has a lower binary.
Droidriven said:
All you need is the correct firmware for your specific model number for your specific region/carrier and the firmware must have a binary that is equal to or higher than the binary of your currently installed firmware. The binary is indicated by the 5th character from the right in the firmware build number. Find that character in the build number of your currently installed firmware and compare it to the same character in the build number of the firmware that you want to flash. If the binary of the firmware that you want to flash is equal to or higher than the binary of your currently installed firmware then you can safely flash it, if the binary is lower than the binary of your currently installed firmware, you will not be able to flash the firmware that has a lower binary.
Click to expand...
Click to collapse
Oh, ok ^ ^ thank you so much!!
I fixed my problems now but i have another problem, i have flashed the bootloader and the twrp but now i am stucked at teamwin logo bootloop thing, i dont know how to fix this any advice? Thank you so much
Oh i forgot, when its like the 2nd or 3rd boot i got a black stripes on the screen, im also trying to press the volume up/down/up and down+power,
Boot into fastbooot and Flash stock boot img.
BadGirlNila said:
Boot into fastbooot and Flash stock boot img.
Click to expand...
Click to collapse
Is fastboot an application or an option in boot settings?
Hi Im trying to root my phone but whenever i do this method i got stuck at bootloop, here is the link
)
And the things i have
Patch security:Sep,2,2021
Device:Samsung-A750FN
OEM:Unlocked
USB debugging:Unlocked
Magisk being used:The one from the link
Any advice how to do it properly? Thank you so much
O
Yatsuko said:
Hi Im trying to root my phone but whenever i do this method i got stuck at bootloop, here is the link
)
And the things i have
Patch security:Sep,2,2021
Device:Samsung-A750FN
OEM:Unlocked
USB debugging:Unlocked
Magisk being used:The one from the link
Any advice how to do it properly? Thank you so much
Click to expand...
Click to collapse
Oh, my : become a sad emoji
Yatsuko said:
Is fastboot an application or an option in boot settings?
Click to expand...
Click to collapse
Bootloader is fastbooot. Boot into bootloader and do it
Hi, i just wanna know if i want to root my phone, is it important to unlock bootloader? And if yes, how should i do it in a samsung a7? Thanks!
Hi, i was planning to root my samsung a7 but i have a question that i dont know the answer, if OEM Unlock is enabled, USB debugging is also already enabled, why my OEM unlocked says bootloader is already unlocked even thought its still blue and not gray? Do i need to void my warranty and make OEM unlock colored gray or is blue enough? Thanks for all advice
MOD ACTION:
@Yatsuko
I had merged your multiple threads into this one yesterday and also sent an alert about it requesting you not to create multiple threads. Today I find that you have created a fresh thread. I have merged that post also in this thread.
With millions of users and messages, the forum is already overloaded. Please do not add to it when you can ask all your questions here.
Thank you!
TNSMANI said:
MOD ACTION:
@Yatsuko
I had merged your multiple threads into this one yesterday and also sent an alert about it requesting you not to create multiple threads. Today I find that you have created a fresh thread. I have merged that post also in this thread.
With millions of users and messages, the forum is already overloaded. Please do not add to it when you can ask all your questions here.
Thank you!
Click to expand...
Click to collapse
Oh, im really sorry,thank you so much