Hi guys, i just ask to some who like me owns the European variant of Honor 6X a clean build.prop file for the model variant and build listed in thread's title, since that I'm trying to figure out a way to fix once and for all the "generic_a15" issue encountered while updating to Magisk V15.0 (i know that there is already V15.1, I'm on it), that was messing up build and model names as you can see in the screenshots attached.
The build.prop in question is located in root/system, and it is only 2KB weight. Attach it here as a file, screenshot it or post it as a .txt log on sites like pastebin, please.
@Nollie8969 @Martin213 i call you guys because i know that we're on the same boat
Although I'm a Ubuntu user, I don't how to become root on android. Show "system files" and ?
Or do I need a terminal app ? If yes, what's the code
Nollie8969 said:
Although I'm a Ubuntu user, I don't how to become root on android. Show "system files" and ?
Or do I need a terminal app ? If yes, what's the code
Click to expand...
Click to collapse
To root on Android usually you just need to flash a SuperSU app like Magisk through a custom recovery l, like TWRP. In order to have a custom recovery, you must have an unlocked bootloader first. The bootloader is unlockable through a code sent by Huawei, wrote in a fastboot string of command by terminal emulator on PC. To be able to see and modify system files, you have to use a root explorer like MiX, ES file explorer, Total Commander, ecc. and browse to the root folder, hidden if not rooted.
I thought you were rooted man, if not don't bother, I'll ask someone else. Thanks anyway for the fast reply
No I have not rooted this phone. Too many strange stories on xda. There is no perfect custom rom yet.
Yeah I'm still on stock too, but i rooted it to take advantage of apps like AdAway, Battery Charge Limit, MiXplorer, Greenify, Xposed and TWRP overall.
I tried the build.prop file for BLN-L21 available in the repository thread, but it contains references to the general model hi6250, and not BLN-L21. I'll update the thread with a correct one as I'll have it
.
Martin213 said:
Hello @RedSkull23 sorry i didn't saw you post If you still need it here you go. Screenshot from my device of needed file.
Click to expand...
Click to collapse
Hi @Martin213 no worries, thanks first of all. I saw that even your build.prop file is the same as mine, and i refer to the fact that it reports in various voices the "generic_a15" as model name, instead of BLN-L21 (as i thought it should be, but I'm still unsure about). Did you messed up with Magisk V15.0 too when it was released? I thought i read that in another thread.. Because that's a thing that makes me think to have a corrupt build.prop file running after that. Even flashing a version.img extracted from official firmware didn't change that, and so i don't know if it had always reported generic_a15 or not... And i notice that even yours contains NRD90M test-keys in various points, so i guess that when you take a TWRP backup, the default name of it is something like "NRD90M_test-keys-xx-xx-xxxx", can you confirm this?
.
I have seen this generic stuff even on some pure stock, rooted phone...my Honor 6X but that was not causing anything in about phone section. I had the NRD tesy key issue yesterday while I restored the TWRP backup while moving from Elite to stock but then eventually gone for the dload to recover it.
Flashed stock and now I am pure stock, non rooted as started using Honor 8 now
Martin213 said:
I didn't play with magisk or testing something,just got notification in status bar and updated. After restart phone went i to a bootloop. Tried flash stock boot.img and M 15.0 zip on top with no success all was the same. After all tryings i flashed boot.img and magisk 14.0 on the top ? Then all went good. This means if i want to update Magisk i have to update my all Rom/firm or at least re-flash same firm ???
P.S one more thing for those who have OEM bootloader option grayed in developer options. Its back to normal(you can turn on/off) when i flashed Magisk and universal safetynet fix 2v beta 5 module. That was really strange for me.
@RedSkull23 if you need any help or collaboration just ask, I'm ready to help you if i can.
Click to expand...
Click to collapse
Kinda weird how OEM unlock came back by Magisk and Safetynet module never got OEM grayed out, but maybe it could help other users..? Anyway, i had understood that build.prop reports generic_a15 since the beginning, so i obtained the answer i was looking for. Thanks for your help!
shashank1320 said:
I have seen this generic stuff even on some pure stock, rooted phone...my Honor 6X but that was not causing anything in about phone section. I had the NRD tesy key issue yesterday while I restored the TWRP backup while moving from Elite to stock but then eventually gone for the dload to recover it.
Flashed stock and now I am pure stock, non rooted as started using Honor 8 now
Click to expand...
Click to collapse
Yeah it must be a general flag that is more specified in others local.prop/componentversion.txt/build.prop files in other root folders, like hw_init or cust... I have my model name correct in phone info and other files, i get NRD90M test-key name only when launch a backup by TWRP, and I'd like to know if other users get that too or they get instead the wrong build name like BLN-L21
RedSkull23 said:
Kinda weird how OEM unlock came back by Magisk and Safetynet module never got OEM grayed out, but maybe it could help other users..? Anyway, i had understood that build.prop reports generic_a15 since the beginning, so i obtained the answer i was looking for. Thanks for your help!
Yeah it must be a general flag that is more specified in others local.prop/componentversion.txt/build.prop files in other root folders, like hw_init or cust... I have my model name correct in phone info and other files, i get NRD90M test-key name only when launch a backup by TWRP, and I'd like to know if other users get that too or they get instead the wrong build name like BLN-L21
Click to expand...
Click to collapse
I am in the same boat. You will fet NRd test in twrp back-up name.
If you like change in model name then there are few changes needs to be done in build.prop file. As long as its appearing correctly in about phone, no need to worry as thats with Kirin phone i guess, had same on 5C, 6X. Dont worry thats nrd stuff jn twrp name is normal. I change it manually there for every backup name
shashank1320 said:
I am in the same boat. You will fet NRd test in twrp back-up name.
If you like change in model name then there are few changes needs to be done in build.prop file. As long as its appearing correctly in about phone, no need to worry as thats with Kirin phone i guess, had same on 5C, 6X. Dont worry thats nrd stuff jn twrp name is normal. I change it manually there for every backup name
Click to expand...
Click to collapse
Ok, I'm not the only one so :victory: yeah i saw but i wanted to know if even others was getting that as default backup name or not. In fact i do the same and i was sure that it was due to the build.prop file located in /system, but i waited to modify that because i thought that if it is was already like that, maybe there was a reason... But maybe there isn't one, just Huawei :silly:
Related
I have an unlocked xperia z3 d6603 I bought brand new in january I believe. I just today rooted and installed recovery but am stuck on the 23.0A.2.93 tft rom which it shippped with. It would have normally been running unrooted the latest rom from sony which was just pushed out a couple months ago. I'm in california and need a rooted d6603 generic global rom, or even unrooted, and I can't seem to find the down link here. In xpreifirm 3.6a latest, I keep getting a java error so can't use that and I've already uninstalled and installed the latest 64bit java8 update 40. I was going to just flash it with the moonwalker rom but it days I need to be on a different tft altogether. Any help here would be appreciated. I have installed a firewall, changed dns servers, and uninstalled a few things using rom toolbox. Hoping to just update it to the recent tft or even better, a working custom rom which won't mess up the default phone capabilities. I'm on kitkat 4.4.4, at&t lte, rom 23.0.A.2.93
Again I need a rooted global generic 577 tft for a z3, a nonrooted one, or even better, a custom one I can just flash to it so I can get back to my life.
since you have a working recovery just flash this one 23-0-1-5-77-deodexed-zipaligned it's the latest KK
ps: I'm on AT&T in CA as well and running that firmware just fine for a while now, it's generic global so no worries...
awesome. THANKS. Gonna try it now. Been at it all day from like 10am to about 5 when I had to break
How do you flash a zip file
tweker said:
awesome. THANKS. Gonna try it now. Been at it all day from like 10am to about 5 when I had to break
Click to expand...
Click to collapse
I rebooted with TWRP in recovery mode, reset device (Wipe Data, Cache and Dalvik Cache), saw no way of flashing from recovery mode. Shut phone off. Plugged in in flash mode with the zip file in the firmwares folder and it was not recognized by flash tool. Where are the directions for flashing a zip?
Choose the second option in recovery
Install custom zip
I used NDR to reboot into recovery. The zip was on both internal and external at root. First time I selected the one from internal and it gave no errors. Wiped cache and rebooted and still on stock 93. Did the exact same thing again choosing zip on sd card and it still says 93. Third time I did it from sd card but no cache wipe. Still on23.0.A.2.93. WTF???
Where can I find a working ftf. NDR doesn't work for ****. BTW, phone is setup in dev mode with mock, airplane mode etc with supersu free working. I think
BTW, why in the hell does the thread with all the roms not have any current ones???? rooted or not
What for are you trying to flash? Please provide a link.
What does the recovery log say? It really helps if you tell us this.
FTF files are geberally not uploaded anymore as it is very easy to download any you want from the sony servers and create your own FTF using flashtool and Xperia firm.
Ps, it may be nice to watch your language. The issue is not NDR, it works fine.
I'm using D6603_23.0.1.A.5.77_deodex.zip from here: http://forum.xda-developers.com/z3/development/deodex-23-0-1-5-77-deodexed-zipaligned-t3015178 on top of D6603_23.0.A.2.93_Generic_20GLOBAL.ftf which was rooted and dual recovered. I have flashed the above 5.77 zip file like 5 times from recovery mode and still on 93. This last time I noticed I had no file mgr. Installed es, mounted system rw like it says to do after root, reflashed the 77 deodexed zip, wiped dalvik and cache, reupdated supersu zip in recovery, rebooted, and stil on93. What am I doing wrong? Is there not a dern ftf file I can use instead? OR, should and could I just wait for another official update?
tweker said:
I'm using D6603_23.0.1.A.5.77_deodex.zip from here: http://forum.xda-developers.com/z3/development/deodex-23-0-1-5-77-deodexed-zipaligned-t3015178 on top of D6603_23.0.A.2.93_Generic_20GLOBAL.ftf which was rooted and dual recovered. I have flashed the above 5.77 zip file like 5 times from recovery mode and still on 93. This last time I noticed I had no file mgr. Installed es, mounted system rw like it says to do after root, reflashed the 77 deodexed zip, wiped dalvik and cache, reupdated supersu zip in recovery, rebooted, and stil on93. What am I doing wrong? Is there not a dern ftf file I can use instead? OR, should and could I just wait for another official update?
Click to expand...
Click to collapse
That is not a ROM file, it does not contain a ROM. It just deodex's your system files if you are on that firmware.
And, No, there is not a FTF you can flash that is rooted. FTF files have to be completely stock as we cannot sign them with Sony's keys as we do not know them. The only way to flash something rooted is via recovery
Post#2 told me I could flash the zip over and it would work. No wonder it doesn't work because it doesn't do anything. I don't want to unlock boot because I may fail official updates. I really just want to update to a working global generic 77 rooted dual recovered system. So basically even if I had the official 77, unrooted, I still couldn't use (nor root) it right? Thanks for the help. I at least know to go another route.
tweker said:
Post#2 told me I could flash the zip over and it would work. No wonder it doesn't work because it doesn't do anything. I don't want to unlock boot because I may fail official updates. I really just want to update to a working global generic 77 rooted dual recovered system. So basically even if I had the official 77, unrooted, I still couldn't use (nor root) it right? Thanks for the help. I at least know to go another route.
Click to expand...
Click to collapse
Post #2 is wrong. Also the thread stated in the first line that a requirement for that to work is that you are already on .77 firmware.
There is no need to unlock your boot.
Just flash a .77 prerooted ROM.
If you cannot find one then make one yourself. Follow the guide in the thread called PRFCreator (Just google it)
Once you have the files downloaded it takes 7 minutes and it is all automated for you
Thank You Very Much. At present I have access to two pc's. One is my roomies (win8.1) and mine (win7). My roomies has some sort of java issue and xperifirm fails right when you click the file you want. Tried fixing java didn't work. Mine is wireless, dns disabled, mac changed, hosts file, and tiny wall fw. Experifrm says no net access even though it works fine. Tried a cable and for the life of me got the same error (couldn't quite reconfigure it to work correctly-pita). If I ever get the file I will do the prfcreator magic, and I'm assuming, flash it through ndr tools in recovery mode. In the mean, I might request an xda user in another thread to grab one for me and post it. Should help lots of people not just me. Again, thank you for your help, saved a lot of hair pulling.
tweker said:
Thank You Very Much. At present I have access to two pc's. One is my roomies (win8.1) and mine (win7). My roomies has some sort of java issue and xperifirm fails right when you click the file you want. Tried fixing java didn't work. Mine is wireless, dns disabled, mac changed, hosts file, and tiny wall fw. Experifrm says no net access even though it works fine. Tried a cable and for the life of me got the same error (couldn't quite reconfigure it to work correctly-pita). If I ever get the file I will do the prfcreator magic, and I'm assuming, flash it through ndr tools in recovery mode. In the mean, I might request an xda user in another thread to grab one for me and post it. Should help lots of people not just me. Again, thank you for your help, saved a lot of hair pulling.
Click to expand...
Click to collapse
Sorry about the confusion, indeed the first link that I provided was just a patch to deodex your room (I always use deodex so I can mod my rom)....anyway you can use this one it's a generic prerooted .77 from the z3 android development section in this forum, then you can patch it with the other one if you have the need to...just follow the instructions in this link and you should be on your way
Again sorry about that first post, I rooted my phone the minute root was available on locked bootloader so it's been some time now
I have been to that link. The only one I can see that says generic global is the 23.0.A.2.93 one. The others say, Generic_DE, Generic_NCB, or Generic_AU. Which looks to me like Deutch, Generic Nordic?, and Australian? Since I speak english and am nowhere near any of those places, I did not touch them. Which one is safe to use and will there be any post config for my locale and radios?? Plus I have no clue what the purpose is of de-odexing the file system (flashing that zip) does. I still have read write issues with apk's I install when I tell them to use my 128gb sd card. I did recover my setup prior to the zip flash you pointed me to which I still have-thank you.
tweker said:
I have been to that link. The only one I can see that says generic global is the 23.0.A.2.93 one. The others say, Generic_DE, Generic_NCB, or Generic_AU. Which looks to me like Deutch, Generic Nordic?, and Australian? Since I speak english and am nowhere near any of those places, I did not touch them. Which one is safe to use and will there be any post config for my locale and radios?? Plus I have no clue what the purpose is of de-odexing the file system (flashing that zip) does. I still have read write issues with apk's I install when I tell them to use my 128gb sd card. I did recover my setup prior to the zip flash you pointed me to which I still have-thank you.
Click to expand...
Click to collapse
1) its called a FTF file not a TFT file. It's a FlashTool File.
2) your sd write card issues are a feature of KK, and nothing to do with any error or bug to do with your phone. Just Google KK write to sd card to read more about it and how to circumnavigate this issue that was deliberately introduced by Google.
3) i have read some of the advice you have banded about in several of the thread here. Some of it is just plain wrong. Although not dangerous to anyones device it may be worth reading and learning a bit more first.
4) please stick to asking questions in just one thread, there is no need to ask in several thread because the first time you did not get an immediate answer
5) you can safely flash a FTF from any region as long as it is for the same model you have. Especially as you are only going to be on that version for a few minutes whilst you root them immediately upgrade.
Ok, great. I'll grab the de one. As for not trying to help; I put down what worked for me. If I don't know everything I can still give input with the little I know. That's how people learn, myself incl. I just got my pc running not two weeks ago so a little overwhelmed with having just rooted as well. Thanks very much for all your help.
tweker said:
Ok, great. I'll grab the de one. As for not trying to help; I put down what worked for me. If I don't know everything I can still give input with the little I know. That's how people learn, myself incl. I just got my pc running not two weeks ago so a little overwhelmed with having just rooted as well. Thanks very much for all your help.
Click to expand...
Click to collapse
No worries. I did not mean to imply that you should not help, only that you should be sure that what you are saying is in fact correct information.
We do all have to learn, but its hard to learn when incorrect information is posted and stated as "fact"
Greg
From install to booted took 4 min. Just had to update supersu and remove a few things. This is awesome! NDR Utils is worth paying for. Now I can finally encrypt my phone. TYSM
First of all, don't get your hopes high, i rooted as traditional method like many others. I'm flashaholic and i started new thread for those who upgraded intentionally or accidentally and now think download would brick their sets. it won't. things are pretty obvious here but i repeat I'm sharing this to people who've upgraded for any reasons and have no clue how to downgrade or achieve root.
So i bought a cell (sm g920V) with preinstalled PI2 (MM6.0.1) . found out pingpong root is avail only for 5.02 . i was afraid to downgrade so i searched more. found out nogat 7.0 DQD1 has root. and can be rooted via cf autoroot. i upgraded and i tried. but it didn't worked. on nougat i did everything. tried every root app (both pc and apk ver) but failed. i decided to go back.
here i found This thread by @toutanje which said even i upgraded to nougat, i can safely downgrade to PK2 (6.0.1) , PH1 (6.0.1) and BOG7 (5.1.1) . i flashed BOG7 (5.1.1) directly because during search i've foundout that there is temporary root available for BOK7, and they both are 5.1.1. i did this because BOG7 is earlier version than BOK7, for this i won't have to downgrade but to upgrade that i did. i flashed BOK7 and headed Here, a thread by @klip1 . there wasn't any clear instructions not links no attachments. but thanks to @MrMike2182 who shared main file Here. BEWARE that you'll lose root each time you reboot, but you can gain it back easily by running root apk simply from your mobile. this is better then not having one.
so if you desperately want root. wherever you're on nougat DQD1 or MM. Downgrade to BOK7.
simply follow instructions there and all you have to do is to flash BOG7 from thread mentioned above (for safety as i did did step and i'm not sure if you may directly downgrage to BOK7), then flash BOK7, odin Sboot file (attached). you'll see some yellow codes above when restart. i was stuck there with bootloop on VZ logo. all you need to do is to factory reset. (by pressing and hold vol + & vol down + power button until you see black screen with options. press vol down and highlight second option factory data and reset. now press home button. )
phone will start normally, goto devloper options, enable usb debug, allow unknown sources and than root it with kingroot apk. done.
Those who prefer SuperSu can get lead from Here thanks to @EvilRubberDuck. but i am not sure about point 3. there is nothing attached at first post. tough little search may lead you to success.
Thanks to whoever took even little interst to make this beast rooted. please try to get permanent root for this device too. if anyone know how to get it, or any more info regarding rooting this device. please share. let me aware. i'll really appreciate that.
NOTE : i take no responsibility of what you do to your mobile. you're doing it with your own consent. if you're unsure what you're doing, don't do it. I, developers/members mentioned and xda are not responsible for ANYTHING or what you do to your phone.
Sharjeel.Khan said:
First of all, don't get your hopes high, i rooted as traditional method like many others. I'm flashaholic and i started new thread for those who upgraded intentionally or accidentally and now think download would brick their sets. it won't. things are pretty obvious here but i repeat I'm sharing this to people who've upgraded for any reasons and have no clue how to downgrade or achieve root.
So i bought a cell (sm g920V) with preinstalled PI2 (MM6.0.1) . found out pingpong root is avail only for 5.02 . i was afraid to downgrade so i searched more. found out nogat 7.0 DQD1 has root. and can be rooted via cf autoroot. i upgraded and i tried. but it didn't worked. on nougat i did everything. tried every root app (both pc and apk ver) but failed. i decided to go back.
here i found This thread by @toutanje which said even i upgraded to nougat, i can safely downgrade to PK2 (6.0.1) , PH1 (6.0.1) and BOG7 (5.1.1) . i flashed BOG7 (5.1.1) directly because during search i've foundout that there is temporary root available for BOK7, and they both are 5.1.1. i did this because BOG7 is earlier version than BOK7, for this i won't have to downgrade but to upgrade that i did. i flashed BOK7 and headed Here, a thread by @klip1 . there wasn't any clear instructions not links no attachments. but thanks to @MrMike2182 who shared main file Here. BEWARE that you'll lose root each time you reboot, but you can gain it back easily by running root apk simply from your mobile. this is better then not having one.
so if you desperately want root. wherever you're on nougat DQD1 or MM. Downgrade to BOK7.
simply follow instructions there and all you have to do is to flash BOG7 from thread mentioned above (for safety as i did did step and i'm not sure if you may directly downgrage to BOK7), then flash BOK7, odin Sboot file (attached). you'll see some yellow codes above when restart. i was stuck there with bootloop on VZ logo. all you need to do is to factory reset. (by pressing and hold vol + & vol down + power button until you see black screen with options. press vol down and highlight second option factory data and reset. now press home button. )
phone will start normally, goto devloper options, enable usb debug, allow unknown sources and than root it with kingroot apk. done.
Those who prefer SuperSu can get lead from Here thanks to @EvilRubberDuck. but i am not sure about point 3. there is nothing attached at first post. tough little search may lead you to success.
Thanks to whoever took even little interst to make this beast rooted. please try to get permanent root for this device too. if anyone know how to get it, or any more info regarding rooting this device. please share. let me aware. i'll really appreciate that.
NOTE : i take no responsibility of what you do to your mobile. you're doing it with your own consent. if you're unsure what you're doing, don't do it. I, developers/members mentioned and xda are not responsible for ANYTHING or what you do to your phone.
Click to expand...
Click to collapse
If you use the SuperSU instead of KingRoot then you can use my installroot script and then the rootatboot if you need to reboot for some reason however if you are not near a PC at the time and you really need to reboot then use terminal emulator from the play store and open it and type su then enter and on the next line type pkill zygote and voila reboots without PC.
MrMike2182 said:
If you use the SuperSU instead of KingRoot then you can use my installroot script and then the rootatboot if you need to reboot for some reason however if you are not near a PC at the time and you really need to reboot then use terminal emulator from the play store and open it and type su then enter and on the next line type pkill zygote and voila reboots without PC.
Click to expand...
Click to collapse
yes i've read this post of yours, i should've added this. Glad you came here and i really appreciate your efforts for s6 users. you've done great job for us.
it'll be great if you attach your script and write or quote your method here too. so users don't have to go through earlier threads and finding things. like me who bought this phone pretty late.
right now i'm using quickreboot apk to get hot reboot which keeps the root. but sometimes when you really need to restart. i see your solution as best.
Sharjeel.Khan said:
yes i've read this post of yours, i should've added this. Glad you came here and i really appreciate your efforts for s6 users. you've done great job for us.
it'll be great if you attach your script and write or quote your method here too. so users don't have to go through earlier threads and finding things. like me who bought this phone pretty late.
right now i'm using quickreboot apk to get hot reboot which keeps the root. but sometimes when you really need to restart. i see your solution as best.
Click to expand...
Click to collapse
OK so my phone is on 5.1.1, it was originally on 7.0 so you can downgrade back to the 5.1.1 firmware.. I've included in the file the eng kernel and eng sboot but there's different versions so this one in my file called boot.tar is from the eng kernel to the S6 G925V so if you're using G920V you need to get the eng kernel for that one.. Now first you put the phone into download mode and flash the eng kernel using odin and after the phone boots then using Windows command prompt navigate using the cd command to where the file is you downloaded called S6rootbyMrMike2182 once you're in there type installroot and the script should run and flash everything needed including busybox and then the phone will reboot (it will also boot just this one time without using the rootatboot because the same codes in this file too) now when you click on the SuperSU app it's going to say it needs to update su ignore it and go right to the play store and install/update the SuperSU from there and then the phone should be rooted and ready to go.. If you ever need to reboot for some reason connect the phone to your PC and open a command prompt in the same folder again and run rootatboot and it will set the phone as permissive again so it boots.. You can unplug it after you see the Verizon logo.. If for some reason you aren't near a computer and you really need to reboot then use terminal emulator from the play store and open it and type su and grant root access and then on the next line type pkill zygote and voila reboots without a computer
If you have KingRoot on your phone and you want to get rid of it to use SuperSU thanks to @Chainfire then use this script that I'm listing below.. Also keep terminal emulator open while you are doing this because you might(not all devices just some) get a continuous annoying popup that prevents you from doing anything (thanks to KingRoots junk) so you'll have to use terminal emulator to kill/end that process in order to continue and after you kill/end that process then go delete it immediately! Links to root with SuperSU and KingRoot removal are below!
S6EdgeRootByMrMike2182
KingRoot removal script
G920V ENG Sboot
By the way I nor XDA-DEVELOPERS is responsible for anything you choose to do to your phone! If something goes wrong, just reflash your original firmware but don't go blaming me nor XDA because I don't have to put this up so please do your research before messing with your phone and as always, make a backup of everything you wish to keep! And no this will not delete or wipe your phone unless you choose to! Links are above. You can change it or whatever just give props where it's due!!
SERIOUSLY MAKE A BACKUP OF ALL YOUR PICTURES ETC ETC BEFORE DOWNGRADING AND I'M NOT KIDDING!!!
MrMike2182 said:
OK so my phone is on 5.1.1, it was originally on 7.0 so you can downgrade back to the 5.1.1 firmware.....
Click to expand...
Click to collapse
great. you completed the thread :highfive:
Didn't know about script removing kr.. wil give it a try for sure. :good:
ok i'm getting confuse here. can you please provide exact files that needed to flash on g920V please ? i mean eng kernel and sboot ? and the file with odin says "G920A_Kernel_Root_5.1.1_S****.tar", A ? isn't A refers to at & t ?
i'm afraid if i may flash wrong file. can you please help me here with exact files needed for us (G920v) ?
and when i'm running installroot via cmd, it execute it goes like it created by you until daemon started successfully for like for five to 8 sec and then disappear. phone doesn't reboot. nothing happens. ,
can anyone confirm if i can directly downgrade to BOK7 ? im currently on DQD1 also can anyone guide me how to actually flash my phone like step wise im new here.. I upgraded to 7.0 but I desperately want root now I've odin installed i just need some1 to teach me how to do it like where to select sboot file and other files
Thanks
Sharjeel.Khan said:
so if you desperately want root. wherever you're on nougat DQD1 or MM. Downgrade to BOK7.
simply follow instructions there and all you have to do is to flash BOG7 from thread mentioned above (for safety as i did did step and i'm not sure if you may directly downgrade to BOK7), then flash BOK7.
Click to expand...
Click to collapse
Muhammad Aliyan said:
can anyone confirm if i can directly downgrade to BOK7 ? im currently on DQD1 also can anyone guide me how to actually flash my phone like step wise im new here.. I upgraded to 7.0 but I desperately want root now I've odin installed i just need some1 to teach me how to do it like where to select sboot file and other files
Thanks
Click to expand...
Click to collapse
welcome here. first things first, i don't mean to discourage you but if you don't know about where to "put sboot and other files", you really shouldn't be doing this. additionally downgrading is a risky process where things get messy due to single mistake .
To answer your question directly, NO. i've read a post somewhere here that we can only downgrade to mentioned (in 1st post) firmware. OP there tried to downgrade to other fw but failed.
and that is exactly why i did long and safe procedure and downgraded to BOG7 and then BOK7. . both are 5.1.
2nd question : you need to put sboot file in "AP" section of odin. (be careful with using it)
i assume you have G920V, which have locked bootloader, my suggestion would be... its not worth it. trust me. even if you downgrade, and rooted too, you'll loose root if you restart your device. and you cannot install recovery and so on. there is no permanent root for this device.
Exchange your device for international version or so, either wait for it and enjoy being on nougat. devs are working on it may be. some claim to root nougat too. better don't downgrade and much better if you stop right there when you don't have basic knowledge about this. you'll end up having paper weight instead of device.
Sharjeel.Khan said:
welcome here. first things first, i don't mean to discourage you but if you don't know about where to "put sboot and other files", you really shouldn't be doing this. additionally downgrading is a risky process where things get messy due to single mistake .
To answer your question directly, NO. i've read a post somewhere here that we can only downgrade to mentioned (in 1st post) firmware. OP there tried to downgrade to other fw but failed.
and that is exactly why i did long and safe procedure and downgraded to BOG7 and then BOK7. . both are 5.1.
2nd question : you need to put sboot file in "AP" section of odin. (be careful with using it)
i assume you have G920V, which have locked bootloader, my suggestion would be... its not worth it. trust me. even if you downgrade, and rooted too, you'll loose root if you restart your device. and you cannot install recovery and so on. there is no permanent root for this device.
Exchange your device for international version or so, either wait for it and enjoy being on nougat. devs are working on it may be. some claim to root nougat too. better don't downgrade and much better if you stop right there when you don't have basic knowledge about this. you'll end up having paper weight instead of device.
Click to expand...
Click to collapse
But on 5.1.1 my battery life was so good now it just keeps draining even on power saving just drain and drain I previously also upgraded using Odin from 5.1.1 to 7.0 (biggest mistake) and i'm regretting it although its much better it terms of improvements and performance i just cant live with this battery life also i need root for WifiKill and to hack in-app purchases .. and i don't reboot my device often..
so if im downgrading to both of these BOK7 or BOG7 i need to use the sboot file u provided right ?
Muhammad Aliyan said:
But on 5.1.1 my battery life was so good now it just keeps draining even on power saving just drain and drain I previously also upgraded using Odin from 5.1.1 to 7.0 (biggest mistake) and i'm regretting it although its much better it terms of improvements and performance i just cant live with this battery life also i need root for WifiKill and to hack in-app purchases .. and i don't reboot my device often..
so if im downgrading to both of these BOK7 or BOG7 i need to use the sboot file u provided right ?
Click to expand...
Click to collapse
alright. nothing to worry about. just downgrade like i mentioned on OP (for safe side as no one here to confirm)
okay so like i said you just need to put the provided file (all credits to original dev/coder) in AP section and flash after you install BOK7. .
i can only tell you about BOK7 as i've done and using this. not G7.
so after to downgrade to bok7, let it boot properly. factory reset your phone, go to download mode and flash attached file using odin. (uncheck all options but f reset time and auto reboot)
phone will restart, and you'll see some green numbers and something when booting. let it boot. go to dev options enable usb debugging. uncheck "verify apps usgin adb" and... root either from kingroot (comes with 100 of ads even on lock screen) or look at this post by MrMike2182 who gave us superSU :victory:
and most important part here : make a backup of everything. and i take no responsibility of what you do to your mobile. you're doing it with your own will. if you're unsure what you're doing, don't do it. I, developers/members mentioned here and xda are not responsible for ANYTHING in any way.
good luck :good:
Sharjeel.Khan said:
alright. nothing to worry about. just downgrade like i mentioned on OP (for safe side as no one here to confirm)
okay so like i said you just need to put the provided file (all credits to original dev/coder) in AP section and flash after you install BOK7. .
i can only tell you about BOK7 as i've done and using this. not G7.
so after to downgrade to bok7, let it boot properly. factory reset your phone, go to download mode and flash attached file using odin. (uncheck all options but f reset time and auto reboot)
phone will restart, and you'll see some green numbers and something when booting. let it boot. go to dev options enable usb debugging. uncheck "verify apps usgin adb" and... root either from kingroot (comes with 100 of ads even on lock screen) or look at this post by MrMike2182 who gave us superSU :victory:
and most important part here : make a backup of everything. and i take no responsibility of what you do to your mobile. you're doing it with your own will. if you're unsure what you're doing, don't do it. I, developers/members mentioned here and xda are not responsible for ANYTHING in any way.
good luck :good:
Click to expand...
Click to collapse
Quick question if i can root my device with this method it possible to install xposed framework via Flashfire?, just a question.
If not possible install xposed not a problem, better root than nothing, and i am not reboot so much, to say nothing.
And like say Muhammad Aliyan, the battery in 7.0 is much more less than 5.1.1
(Sorry for my bad english.)
LuisElListo said:
Quick question if i can root my device with this method it possible to install xposed framework via Flashfire?, just a question.
If not possible install xposed not a problem, better root than nothing, and i am not reboot so much, to say nothing.
And like say Muhammad Aliyan, the battery in 7.0 is much more less than 5.1.1
(Sorry for my bad english.)
Click to expand...
Click to collapse
i have tried it earlier and failed but now when i saw youre asking this, i gave it another try and i'm stuck on bootloop. lol.
better don't do it.
i've read it that xposed is not compatible to our devices (64bit) yet ( just read it not confirming it) + in xposed official thread, it has been warned that bootloops occur in samsung stock roms. soi'd say do not try this.
Sharjeel.Khan said:
i have tried it earlier and failed but now when i saw youre asking this, i gave it another try and i'm stuck on bootloop. lol.
better don't do it.
i've read it that xposed is not compatible to our devices (64bit) yet ( just read it not confirming it) + in xposed official thread, it has been warned that bootloops occur in samsung stock roms. soi'd say do not try this.
Click to expand...
Click to collapse
So close, well better wait to safe method in stock room, or unlock bootloader. Thanks anyway.
Sharjeel.Khan said:
alright. nothing to worry about. just downgrade like i mentioned on OP (for safe side as no one here to confirm)
okay so like i said you just need to put the provided file (all credits to original dev/coder) in AP section and flash after you install BOK7. .
i can only tell you about BOK7 as i've done and using this. not G7.
so after to downgrade to bok7, let it boot properly. factory reset your phone, go to download mode and flash attached file using odin. (uncheck all options but f reset time and auto reboot)
phone will restart, and you'll see some green numbers and something when booting. let it boot. go to dev options enable usb debugging. uncheck "verify apps usgin adb" and... root either from kingroot (comes with 100 of ads even on lock screen) or look at this post by MrMike2182 who gave us superSU :victory:
and most important part here : make a backup of everything. and i take no responsibility of what you do to your mobile. you're doing it with your own will. if you're unsure what you're doing, don't do it. I, developers/members mentioned here and xda are not responsible for ANYTHING in any way.
good luck :good:
Click to expand...
Click to collapse
everything was good I downgraded to BOG 7 first with odin all good then OK7 and again all good successfully booted up everything is fine fingerprint sensor etc right after i flash the sboot file my fingerprint sensor stopped working it says an error occurred can you please help me .. phone is rooted though but cmon fingerprint sensor i can't live without it..
Edit: tried factory reset and restarting, none worked.
edit2: reflashed OK7 again and its fingerprint is working but can't root. flashed sboot to root but fingerprint stopped working.
edit3: again flashed OK7 then sboot again green text in the corner again root succeed but again fingerprint not working guess something wrong with the sboot..
Muhammad Aliyan said:
everything was good I downgraded to BOG 7 first with odin all good then OK7 and again all good successfully booted up everything is fine fingerprint sensor etc right after i flash the sboot file my fingerprint sensor stopped working it says an error occurred can you please help me .. phone is rooted though but cmon fingerprint sensor i can't live without it..
Edit: tried factory reset and restarting, none worked.
edit2: reflashed OK7 again and its fingerprint is working but can't root. flashed sboot to root but fingerprint stopped working.
edit3: again flashed OK7 then sboot again green text in the corner again root succeed but again fingerprint not working guess something wrong with the sboot..
Click to expand...
Click to collapse
thats strange because i had FP working while rooted from same sboot file that i attached.
try downloading from another source like in second post where mrmike2182 shared it. and try removing Samsung account (if its there, don't forget to turn off reactivation lock before that.)
see if it helps.
Sharjeel.Khan said:
thats strange because i had FP working while rooted from same sboot file that i attached.
try downloading from another source like in second post where mrmike2182 shared it. and try removing Samsung account (if its there, don't forget to turn off reactivation lock before that.)
see if it helps.
Click to expand...
Click to collapse
Same issue with this flash OK7 FP work ok, but install Sboot and FP not working.
edit1: cant root the device i open cmd with adm permission, installroot, daemon is stop, is starting, after close cmd and the phone not reboot.
LuisElListo said:
Same issue with this flash OK7 FP work ok, but install Sboot and FP not working.
edit1: cant root the device i open cmd with adm permission, installroot, daemon is stop, is starting, after close cmd and the phone not reboot.
Click to expand...
Click to collapse
hmm. i believe FP didn't came friendly with this sboot. any experienced dev might help us out here
make sure you have proper drivers installed and have working adb. read instructions, search fourm. by the way, for same kind of issues, i had to go with kingroot.
Sharjeel.Khan said:
hmm. i believe FP didn't came friendly with this sboot. any experienced dev might help us out here
make sure you have proper drivers installed and have working adb. read instructions, search fourm. by the way, for same kind of issues, i had to go with kingroot.
Click to expand...
Click to collapse
Well better than nothing, uninstall all bloatware for my phone (finally), FP sensor yes it to cool but, meee y si better pin or patron.
Just have to try install Xposed and all done.
Do you try to install official xposed? Or the unofficial for Samsung Stock https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
LuisElListo said:
Well better than nothing, uninstall all bloatware for my phone (finally), FP sensor yes it to cool but, meee y si better pin or patron.
Just have to try install Xposed and all done.
Do you try to install official xposed? Or the unofficial for Samsung Stock https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Click to expand...
Click to collapse
i'd love to try right now but i can't because i'm currently working on something else.
but for your assistance, Here is what you're looking for. its a success.
Sharjeel.Khan said:
i'd love to try right now but i can't because i'm currently working on something else.
but for your assistance, Here is what you're looking for. its a success.
Click to expand...
Click to collapse
I try a shoot.
Its working, its ****ing working, I sacrifices FP, and Supersu but I dont mind i have xposed and a root.
imgur(dot)com/a/zLvrD
Edit1: bad news activated module xposed requeried reboot, soo the root is lost and requiered to root again with kingroot the problem is my percent is not advance 01%. Also every time I rooted the phone is slowing arriving a point where it restarted alone and is only 01%.
If i a factoy reset i lost xposed and root or better reflash the Rom OK7?
Hi all,
Someone know How can I Root my device?
You can not yet...
First stage would be unlocking the bootloader ... which Huawei now deny you the ability to do.
However it appears someone is offering a working unlock service.
People are reporting it's legit for the P20 / Pro.
Be careful though.
https://forum.xda-developers.com/huawei-p20-pro/development/bootloader-unlock-service-t3852447
mudnightoil said:
First stage would be unlocking the bootloader ... which Huawei now deny you the ability to do.
However it appears someone is offering a working unlock service.
People are reporting it's legit for the P20 / Pro.
Be careful though.
https://forum.xda-developers.com/huawei-p20-pro/development/bootloader-unlock-service-t3852447
Click to expand...
Click to collapse
As a fresh owner of Honor Note 10 I was curious if it's possible to have the bootloader unlocked. Just finished chatting to the admin from the website and he claims that YES, they offer this service for 30EUR. But then I asked him if there's an actual way to root the device and he wouldn't know. My point here is: there's not much of a point to have an unlocked bootloader if you can't get the root on the phone. I think we will have to wait a bit longer till someone gets a working root method. I wouldn't mind to pay for having the bootloader unlocked (for reasonable amount of moneyh) as long as it works...
You can't have root without the unlocked bootloader.
So of course there isn't a root method yet ... because no-one was previously able to unlock the bootloader.
If that is now possible, then a root method will inevitably come.
mudnightoil said:
You can't have root without the unlocked bootloader.
So of course there isn't a root method yet ... because no-one was previously able to unlock the bootloader.
If that is now possible, then a root method will inevitably come.
Click to expand...
Click to collapse
Given Huawei's recent dull attitude that reads something like "LOCKED BOOTLOADER is for your safety only" (BLAH BLAH BLAH), reasonable doubt of a commonly available ROOT for this magnificent device is more than imminent...
But hope is all there's left, right
If one enterprising individual has found a way, and is charging €30, then others will find a way too, and will provide it for less / nothing eventually.
He's just the first, and good for him.
mudnightoil said:
If one enterprising individual has found a way, and is charging €30, then others will find a way too, and will provide it for less / nothing eventually.
He's just the first, and good for him.
Click to expand...
Click to collapse
Hmmm... there seems to be some work in progress alright regarding a custom TRWP for Note 10, if the google translator works fine, that is:
https://translate.google.com/transl...m/thread-17327282-1-1.html&edit-text=&act=url
And the bootloader unlock code might get somewhat cheaper, too:
https://global-unlocking-solutions.miiduu.com/bootloader-unlock-codes-choose-model-below
Let's wait and see, I guess
Just to keep this thread alive, does anyone happen to have an access to the Chinese Huawei club forum with TWRP recovery? I'm unable to download the img file there as it requires to have a chinese phone number to register on the site. All it takes is to have that file downloaded. I'd like to volunteer to unlock the bootloader, then flash the TWRP through adb interface and try to root the Note 10 with Magisk or SuperSU just to see if it works.
Anyone with Chinese Huwaei ID willing to download that file, as seen here:
https://club.huawei.com/thread-17327282-1-1.html
Any help is much appreciated!
7gismo said:
Just to keep this thread alive, does anyone happen to have an access to the Chinese Huawei club forum with TWRP recovery? I'm unable to download the img file there as it requires to have a chinese phone number to register on the site. All it takes is to have that file downloaded. I'd like to volunteer to unlock the bootloader, then flash the TWRP through adb interface and try to root the Note 10 with Magisk or SuperSU just to see if it works.
Anyone with Chinese Huwaei ID willing to download that file, as seen here:
https://club.huawei.com/thread-17327282-1-1.html
Any help is much appreciated!
Click to expand...
Click to collapse
i have downloaded but you need to have unlocked bootloader. i had also registered for that xda huawei unlocker thread, but stll waiting for unlock key.
Here : https://1drv.ms/u/s!AizwhfImY2xzgadtepfbKJ1BQqxMvg
---------- Post added at 02:08 PM ---------- Previous post was at 01:57 PM ----------
Can anyone download Official rom 108 from below baidu link. Atleast it will be useful for recovery if something screwsup. baidu is somehow extremely slow to download and connection resets for me after few hours. Please share once you are able to download.
https://pan.baidu.com/s/1-JF43jLbz2WcTMurYHm0Hw
Password : 6c52
Process :
Unzip the compressed file and copy the dload folder to the SD card.
forced upgrade:
1. Simultaneously press and hold the Note10 three physical buttons (volume up and down keys, power button) until you enter the recovery to upgrade
2. If the upgrade is successful, the machine will automatically restart into the system;
Tip: If there is a problem with the upgrade failure, please check whether the SD card upgrade package is copied to the specified directory and the upgrade package is the SD card upgrade package of the product.
Thanks for the help, much appreciated?.
The good news is I got my bootloader unlocked. The bad news is the apk file requires root, which I was hoping to obtain by flashing a custom TWRP image. I thought that's what it was available in that Huawei club Note10 forum...
Ah well, we have to remain patient till someone actually releases a working TWRP for Note 10. Sooner or later, I guess ?.
Cheers!
7gismo said:
Thanks for the help, much appreciated?.
The good news is I got my bootloader unlocked. The bad news is the apk file requires root, which I was hoping to obtain by flashing a custom TWRP image. I thought that's what it was available in that Huawei club Note10 forum...
Ah well, we have to remain patient till someone actually releases a working TWRP for Note 10. Sooner or later, I guess ?.
Cheers!
Click to expand...
Click to collapse
How did you got it unlocked?
i know there are many pid sources but was waiting for someone to confirm they really work for note 10. Can you please share where you got it from?
Sure, I've posted the link already:
https://global-unlocking-solutions.miiduu.com/bootloader-unlock-codes-choose-model-below
I chose the fast 1-20min option and it was done that way, indeed. You must pay upfront, of course. They generated the unlock code for me and all I did was a few lines in cmd powershell while phone was in fastboot mode.
There's an ugly message coming up everytime I boot saying that my device has an unlocked bootloader?
But we need a custom CWM or TWRP image now?
I wonder if there's a stock boot image of Note 10 floating around online, perhaps in Huawei Chinese forums?
---------- Post added at 04:28 PM ---------- Previous post was at 03:35 PM ----------
bark1234 said:
Can anyone download Official rom 108 from below baidu link. Atleast it will be useful for recovery if something screwsup. baidu is somehow extremely slow to download and connection resets for me after few hours. Please share once you are able to download.
https://pan.baidu.com/s/1-JF43jLbz2WcTMurYHm0Hw
Password : 6c52
Process :
Unzip the compressed file and copy the dload folder to the SD card.
forced upgrade:
1. Simultaneously press and hold the Note10 three physical buttons (volume up and down keys, power button) until you enter the recovery to upgrade
2. If the upgrade is successful, the machine will automatically restart into the system;
Tip: If there is a problem with the upgrade failure, please check whether the SD card upgrade package is copied to the specified directory and the upgrade package is the SD card upgrade package of the product.
Click to expand...
Click to collapse
Just did some digging there and actually, you can find a working firmware file 125 for Note 10 online. Chances are even the latest 132 build is there somewhere on Chinese forums...
I'd recommended you to get the bootloader unlocked from the link above, if you have a good idea how to proceed with root? My skills are way too limited, I'm afraid?.
The good news is I got my bootloader unlocked. The bad news is the apk file requires root, which I was hoping to obtain by flashing a custom TWRP image. I thought that's what it was available in that Huawei club Note10 forum...
Thanks for your reports.
TWRP image file is included in K-RecTools_8e.apk.
Rename apk to zip and decompress it, you can get the twrp.img.
i will be a Guinea pig and see if it works. i should have my bootunlock code from the link above soon and looks like we have a twrp (hopefully it works) from a few posts back. i shall try and download fhe 108 firmware just in case i get bricked. when i get home. will keep you guys posted.
TWRP INSTALLED MAGISK 17.1 FLASHED AND SAFETYNET PASSED. ADWAY INSTALLED, SUCCESS
NOTE I AM ON B132 AND IT TRYS TO GET ME TO INSTALL B132 THROUGH SYSTEM UPDATE WHICH IS 3.9GIG
mudnightoil said:
If one enterprising individual has found a way, and is charging €30, then others will find a way too, and will provide it for less / nothing eventually.
He's just the first, and good for him.
Click to expand...
Click to collapse
trd_jzx100 said:
i will be a Guinea pig and see if it works. i should have my bootunlock code from the link above soon and looks like we have a twrp (hopefully it works) from a few posts back. i shall try and download fhe 108 firmware just in case i get bricked. when i get home. will keep you guys posted.
TWRP INSTALLED MAGISK 17.1 FLASHED AND SAFETYNET PASSED. ADWAY INSTALLED, SUCCESS
NOTE I AM ON B132 AND IT TRYS TO GET ME TO INSTALL B132 THROUGH SYSTEM UPDATE WHICH IS 3.9GIG
Click to expand...
Click to collapse
OK now. I managed to flash TWRP on the phone successfully. However after i tried to flash Magisk, the phone remains unrooted So it's a no for me. Any idea why?
There's a red error stating coming up twice: failed to unmount '/system' (Device or resource busy). But the Magisk zip get installed anyway. So what am I doing wrong?
EDIT: the bloody TWRP is password protected. My pin password doesn't do the trick...
EDIT 2: OK, just removed my lock screen in phone settings, no errors in TWRP anymore. But after I flashed Magisk (no erros again), phone still remains unrooted? What the hell?
What version magisk are you using
trd_jzx100 said:
What version magisk are you using
Click to expand...
Click to collapse
Nevermind now. I had to install the Magisk manager app additionally and the root became visible then. First thing installed was adaway?.
Thank you for your time and help.
___________________________________________
BIG THANKS goes to tensoba and trd_jzx100 for their tips and participation ?. But most of all bark1234 is the one who made all of this possible after he kindly provided us with the crucial apk file containing TWRP image.
Ladies and gentlemen, Huawei honor note 10 can be rooted now.
Awesome mate. Finally we have proper way to root.
Can you please create a thread and mention process to root for others for follow.
7gismo said:
Nevermind now. I had to install the Magisk manager app additionally and the root became visible then. First thing installed was adaway.
Thank you for your time and help.
___________________________________________
BIG THANKS goes to tensoba and trd_jzx100 for their tips and participation . But most of all bark1234 is the one who made all of this possible after he kindly provided us with the crucial apk file containing TWRP image.
Ladies and gentlemen, Huawei honor note 10 can be rooted now.
Click to expand...
Click to collapse
bark1234 said:
Awesome mate. Finally we have proper way to root.
Can you please create a thread and mention process to root for others for follow.
Click to expand...
Click to collapse
I'll see what I can do. The least I can do is to create a brief tutorial how to root this beauty of a phone?.
Thanks again for your tremendous help
Resolved - L29C567B190->Build NRD90M Test-keys-> DLOAD fix fails -> Now Boot Looping
I've been working on the path to have my Mate 9 unlocked, rebranded, and to Pie.
I followed this guide. Not sure why, but I ended up with this:
TWRP Recovery (expected thisi)
Not upgraded to Oreo (unexpected)
Build: NRD90M Test-keys (unexpected and problematic)
I've read that I need to re-install the MHA-L29C567B190 again.
So, I attempted 2-3 times with different downloaded (supposedly MHA-L29C567B190) firmwares to just use TWRP to upgrade. All failed. So, I decided to put a DLOAD directory with the files required onto my SD card and upgrade from the Project Menu.
Of course, I had to reinstall the default recovery to do that. I did that using fastboot.
So at this point, I'm thinking I can do the reinstall of MHA-L29C567B190. So, I did this:
Launched Project Menu (*#*#2846579#*#*)
Select 4. Software Update
1. SDCard Upgrade
Phone restarts and starts the upgrade
I get this message
Software install failed!
Incompatibility with current version. Please download the correct update package.
Click to expand...
Click to collapse
So I presume I get that error because NRD90M Test-keys doesn't even have any compatible versions. I am certain I downloaded the files for MHA-L29C567B190.
Anyone have any suggestions how I can reinstall the Nouget MHA-L29C567B190 over NRD90M Test-keys?
If I can get that fixed, I can struggle again with rebranding.
Any help appreciated.
So, I went out and studied the rebrand instructions, and finally found that I misspelled the HWOTA directory on the SD Card. So I ran that again.
This time it appeared to be working on the install of the 432 software at the end of the process. But it failed for some reason.
Now I'm in a boot loop. My very first. Should I celebrate my first?
So, now on a search to find how to get out of the boot loop. I've tried the various options I do have from the boots into recovery. Exact naming of process I list below may not be accurate, but you'll probably get the idea:
Tried the option to download latest version and image...failed
Tried doing a factory reset...failed
Tried following the rebrand process once more. same results.
Update on attempt to fix bootloop...
I followed this article to repair. I downloaded a fresh c567b190 file, and copied the update.app into dload. Did a force install per the instructions...it failed.
I had another one from a different download site. It failed.
I tried a 432 file from what I was trying to rebrand to. It failed. I do find it interesting that supposedly same files downloaded from different sites are different sizes. As well, some instructions say to only copy update.app to dload, and others say to copy entire set of files/folders that are in the file that update.app is in.
Beginning to worry this phone is toast.
I'm going to search out other 'remedies'.
[EDIT]
I'm pretty sure that the build showing as NRD90M is causing my problems. I suspect the bootloader is checking against the version and "nothing is compatible" with it. So being in a bootloop with the additional problem of wrong build identification is making this difficult.
I don't know if anyone after weekend will see this and/or have any suggestions, but I'll keep updating as I learn things or stumble onto new obstacles.
I do have some success to express.
I used this thread and it got me booted, into Oreo, and a good build.
BUT...(as always)
The instructions on that thread are to unbrick, and install the rebrand files at the same time. However, during the TWRP Install process (after getting Oreo 8.0.0.046(0409) installed. It was supposed to boot into TWRP after installing it, and do that update.
But, yet another error: during TWRP install attempt, got an error about partition size (don't recall if it was too long or short or what. If anyone needs to know to help me get past this I can run it again).
So, the batch file was waiting at a prompt for me to load TWRP so it could continue. But no TWRP. So I found a TWRP for Oreo, and installed it. I then hit the ENTER key for it to continue, but it didn't.
I loaded Firmware Finder on the phone, and it found nothing to work with it. I have no idea what Oreo 8.0.0.046(0409) is even for, or what region it would be from. Can't find it even with Google.
So, here's what I need help with
What's the best way to get to MHA-L29 C432(Europe). Would it be as simple as adding my l29 model in FF, downloading c432, and installing via TWRP? Another way better?
I think I'm off of the keyboards and phone for a while. It's been quite a chase.
Hopefully I'll get some feedback early next week on how to progress.
u need find oem with hw eu region with l29, then phone can accept update
kikson112 said:
u need find oem with hw eu region with l29, then phone can accept update
Click to expand...
Click to collapse
I as thinking I had the right firmware, MHA-L29C432B194. But as I think about it, I didn't get that from FF. When I add a model of MHA-L29C432B194 in FF, and search, I find it, but I'm not sure which one I need. I understand I need FullOTA-MF-PV for dload. What is there is FULLOTA-MF, and OTA-MF . I suspect it depends on which method of install I use.
I"m thinking about trying booting to TWRP, and 'install' the ZIPS for the firmware. But I haven't seen confirmation that will work. I don't want to end up in another bootloop.
at the end what u want to do ? tell me ?
kikson112 said:
u need find oem with hw eu region with l29, then phone can accept update
Click to expand...
Click to collapse
kikson112 said:
at the end what u want to do ? tell me ?
Click to expand...
Click to collapse
I have fixed the bootloop problem from a search that I found a tutorial. The problem now is that it left me on an Orea that oeminfo (cust) is lost. It's not recognized as a valid rom.
I have another thread that has migrated to this topic. I think someone there is gathering tools for me.
I apparently need to downgrade to Nouget, and start over my efforts to migrate to c432, which then will auto upgrade me to Pie. Problem so far at this point is finding a good HWOTA8 file. All searches I find that have links are dead links.
if someone gather it let him work. give me what exacly rom u need, full name
Sorry. I am not getting the email notifications of updates. Apparently sometime in the past, I opened a different account here with my current email. It won't let me update my email address here as it is used in that other account. I've tried the Forgot password thing, but the reCAPTCHA just circles and circles and never lets me make the request.
Back on topic: I got it all worked out. I had another thread on topic of the beginning of my process that was pretty much done. But conversation struck back up, and it continued on to a fix for this problem. It's a bit lengthy, and I learned a lot there, thanks to @zgfg.
If anyone wants to see how this was resolved, you can start at Post # 60 at this thread.
Thanks folks for your input here.
I followed a tutorial by Max on XDA's youtube channel (I'm a new user so unfortunately I cannot provide the link but I'm sure you can find it if you wish)
First mistake was going into this thinking it was a simple process to unlock bootloader, install TWRP, and root with Magisk . . .
Anyways I was looking for the fast boot files linked in the description of the video (my build number is 10.3.4 GM21AA) But could not find any past 10.0.5 (which was the most recent uploaded). [Cannot post the link however it is posted on androidfilehost]
I decided to go with the 10.0-GM21AA-OnePlus7ProOxygen_21.O.20_OTA_020_all_1909172051_db7a3f61-FASTBOOT.zip file, i dug into the images.zip folder to find the boot.img file (which is the one I used in my rooting process)
I followed the steps exactly as Max did them in his video but ended up with no camera working, no cellular network, cannot toggle the wifi on, no sound through speakers . . . now suddenly my phone has become a standard wallpaper background and nothing else.
Freaking out (but also I should've known what i was getting into being as naive as I am) I contacted OnePlus Support which basically told me my warranty is void now . . .
I guess I have no choice but to figure out how to root this properly or my 1000$ phone goes into the trash
Do I need to find the boot.img file for the One Plus 7 Pro Oxygen 10.3.4 GM21AA? Was that the mistake I made that messed up everything by deciding to flash the wrong boot.img
Any help is much appreciated!
Thanks guys!
https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/amp/
GeekMcLeod said:
https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/amp/
Click to expand...
Click to collapse
Thanks for your rapid response however that doesn't seem to do it for me I still cannot access camera, wifi, phone calling, and there is no sound . . .
[EDIT] I think I have discovered the problem however I do not know how to fix it. I flashed the wrong boot img file. Issue is that I do not know where to find the boot.img for 10.3.4
The best medicine against such issues is to MSM tool. I'm using you have the 1917, 1910 models i.e. the global editions and not the EU version. If you have EU version, I don't know if the MSM tool will work. Next, if you have successfully complete the MSM setup, then you can go about rooting the device by following this tutorial https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
On a side note, I have been swinging between root and full stock and frankly I don't see the real need to root the device. Stock unrooted OOS is really a good OS and rooting really doesn't add much value IMO.
rapurepie said:
I followed a tutorial by Max on XDA's youtube channel (I'm a new user so unfortunately I cannot provide the link but I'm sure you can find it if you wish)
First mistake was going into this thinking it was a simple process to unlock bootloader, install TWRP, and root with Magisk . . .
Anyways I was looking for the fast boot files linked in the description of the video (my build number is 10.3.4 GM21AA) But could not find any past 10.0.5 (which was the most recent uploaded). [Cannot post the link however it is posted on androidfilehost]
I decided to go with the 10.0-GM21AA-OnePlus7ProOxygen_21.O.20_OTA_020_all_1909172051_db7a3f61-FASTBOOT.zip file, i dug into the images.zip folder to find the boot.img file (which is the one I used in my rooting process)
I followed the steps exactly as Max did them in his video but ended up with no camera working, no cellular network, cannot toggle the wifi on, no sound through speakers . . . now suddenly my phone has become a standard wallpaper background and nothing else.
Freaking out (but also I should've known what i was getting into being as naive as I am) I contacted OnePlus Support which basically told me my warranty is void now . . .
I guess I have no choice but to figure out how to root this properly or my 1000$ phone goes into the trash
Do I need to find the boot.img file for the One Plus 7 Pro Oxygen 10.3.4 GM21AA? Was that the mistake I made that messed up everything by deciding to flash the wrong boot.img
Any help is much appreciated!
Thanks guys!
Click to expand...
Click to collapse
Roll back to 10.3.3 and use the patched boot.img from here: https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
Thanks everyone. I finally solved the issue
From what I know, it's practically impossible to brick a Onleplus, I lost two Samsung's, and a LG, relocking bootloader while rooted, rushing to get the phone up, and forgetting to uninstall Magisk, TWRP, haven't ever had that problem with OnePlus or Xiaomi devices though. I've relocked this bootloader a couple of times while rooted, and nothing happened. Root is still very necessary for me, I don't buy anything I can't hack. I just noticed icon burn-in on my notifications bar, really pissed.