Database Develop

VIE-L09 seems to be totally screwed!

Hey,
So i used the SRK tool to try and root my VIE-L09C40 (P9 Plus)
Something seemed to happended during the rooting procedure and when i entered e-recovery it said it had to Download a new version, but couldnt connect to internet via wifi.
Any ways it seemed to work after a while but now i have no keyboard at all, so i cant literally start my phone.
it starts, boots the EMUI 5.0 logo and goes through the information a terms, i click the ok button and thats fine.
Next it tells me to sign in to my wifi, i select my wifi and when i go to type the password all i have is google voice as a keyboard, ive searched and searched but cannot find a way around it, also the frp has tripped on phone so i cannot log in to my google account without a keyboard.
How can i get around this?
do i have to flash parts of firmware?
any help would be great, i sent it away to hauwei and they say warranty void due to software!, can only assume something wrong was flashed?
Waiting for phone to be returned now, please help

I had the exact same issue last night as well. No keyboard and only an option to enter details with voice.
Ended up with an essentially bricked phone. Couldn't find any info on the problem online, so I have to improvise.
I'm starting from scratch after formatting etc. using stock oeminfo, recovery and rolling back to Marshmallow. (fingers crossed ADB will let me, because it was giving me errors before)
Will let you know if I'm successful and the steps I took.
=====================
tolerant said:
Hey,
So i used the SRK tool to try and root my VIE-L09C40 (P9 Plus)
Something seemed to happended during the rooting procedure and when i entered e-recovery it said it had to Download a new version, but couldnt connect to internet via wifi.
Any ways it seemed to work after a while but now i have no keyboard at all, so i cant literally start my phone.
it starts, boots the EMUI 5.0 logo and goes through the information a terms, i click the ok button and thats fine.
Next it tells me to sign in to my wifi, i select my wifi and when i go to type the password all i have is google voice as a keyboard, ive searched and searched but cannot find a way around it, also the frp has tripped on phone so i cannot log in to my google account without a keyboard.
How can i get around this?
do i have to flash parts of firmware?
any help would be great, i sent it away to hauwei and they say warranty void due to software!, can only assume something wrong was flashed?
Waiting for phone to be returned now, please help
Click to expand...
Click to collapse

dmccort said:
I had the exact same issue last night as well. No keyboard and only an option to enter details with voice.
Ended up with an essentially bricked phone. Couldn't find any info on the problem online, so I have to improvise.
I'm starting from scratch after formatting etc. using stock oeminfo, recovery and rolling back to Marshmallow. (fingers crossed ADB will let me, because it was giving me errors before)
Will let you know if I'm successful and the steps I took.
=====================
Click to expand...
Click to collapse
Good luck, i did read that it might be possible to install the base firmware back to it and then update again.
Im sure we are not the only people this has happened to and if you succesfully do this, maybe consider making a full step by step guide so to help others.
Fingers crossed
:good:

Will do my best.. So far it's been a major. I've managed to flash a working stock ROM and boot up. But there are a few things to smooth out. Such as, I have no IMEI number now and the build is C900, also the bootloader is modified.
To get it to boot I had to use DC- Phoenix to flash a factory firmware(Chinese) which I had to pay for. Then I flashed a stock vie-l09c432b181 ROM over the top.
To repair the IMEI I'll have to use HCU, which I'll have to pay for as well. But that's ok. If I can get my original IMEI back, I can use the original unlock code I got earlier this year, otherwise I'll have to get a new one based on a new IMEI.
I can repair the bootloader and region code using twrp etc. so that's not a problem.
I'm actually using the phone to write his reply, so I can at least use it.
Once I have it all 100% working I'll try to put together a full step by step.
Cheers.

Well, I have a working phone. But, it'snot stable. Having trouble with mobile connection, sms, mms, 4g etc not staying connected. So wont be doing any write-ups just yet.
Not until it's stable.
I'm wanting to return it to complete stock now. And that requires trying to find an oeminfo file for C706 (New Zealand).
Will add more as I get there. Sorry.

I had the same problems. All I did is updated the phone with the firmware you want via Twrp . Be warned that it will replace the recovery back to stock. Also clear the cache and etc.

I had a similar issue with SRK tool, bootlooping, won't flash new firmwares, lost all the stock apps and diagnostic tools.
I'm now stuck on a TEST-KEYS build with no NFC or Bluetooth.
My solution was to throw the piece of junk in a drawer, forget about it and I went and bought a Pixel XL instead - a phone that is properly supported and gets updates quickly.

After much messing and a headache I finally got to c432b370
And everything back to normal

tolerant said:
After much messing and a headache I finally got to c432b370
And everything back to normal
Click to expand...
Click to collapse
How did you succeed?
I am stuck on TEST-KEYS but I am not able to flash other roms on it. When I go to recovery, the update process stops after a while
Sent from my VIE-L09 using Tapatalk

ROG Phone II (Tencent, thought was global), Can't boot after Root attempt.

Hey all- after noticing my Netflix wouldn't work despite being a WW plastered phone, I discovered that my phone was actually a flashed CN version. I noticed that I can't receive updates- security or otherwise, which was a big motivating factor for me to try and fix it.
Eventually, I posted on Reddit because I was fed up
My build is (was) - WW_16.0650.1908.12_0
One dude sent me to this video- and since I have dealt with rooting before on my Nexus 4 I decided to try it out.
"
ASUS ROG 2 FULLY CONVERTED GLOBAL ROM WITH WORKING THEMES AND UPDATES"
I can't post links because my account is currently too new.
I followed the guide exactly, but when I got to the part where it said to use ADB, my attempt to boot the rootww190812.img failed- someone said to try on B instead, that also failed. It said it "failed to load/authenticate boot image.
From now it has been bootlooping into the Qualcomm
"qualcomm crash dump mode"
"waiting for flashing ramdump"
And I can not boot the device. I can still reach Fastboot, but that is all.
How can I fix my phone- preferably including continuing the boot process but at this point i'd be happy just to have a working phone again.
Edit: I have found factory reset- but i'm not sure if I should do it, or if I risk simply undoing and having to re-do the initial global reflash.
Edit 2: factory reset says WW_I001D and says it will go back to 1908.12. it should be safe I assume-
Edit 3: changing back to A allowed it to boot without factory reset- but it still won't root, build is now WW_16.0640.1908.12_0

https://forum.xda-developers.com/rog-phone-2/how-to/guide-to-check-change-fingerprint-cn-to-t4002279
This guide ended up helping me- I got it fixed, delete this post if you want.

SM-N9200 Odin to TWRP CHINESE FAIL

Hi all here is my dilemma concerning my personal DD, the phone was bought new in 2015-6 brand new and is currently on Android 7.0! The phone is in my opinion still very relevant and can be made even more so (if) I can update the whole firmware to the recent Note10 UI as seen elsewhere??
The trouble that I have experienced is trying to install TWRP via Odin? What happens, it recognises the file to be used, I set the parameters and start! It moves reasonable quickly then suddenly stops - No errors on the Pc/Odin page BUT the phone moves from the download mode in English to Chinese with Warning triangle and remains there until I reboot phone which starts up as normal??
I cannot get past this, and do Not know why the Change to Chinese that I do Not read or understand, so I have a few Pics but the 2 that I think are telling I will add if possible?
I found something in an overall search via the net, but this was the only one and this though Unclear in it self did Not assist me! Would I be correct in saying that this may be unique in that neither pictures or any where as this error arose hence why my possible struggles? Please can someone help in Solving this puzzle thank you.

Galaxy Note 9 stuck at bootloop after update Magisk

I was happily use my Note 9 N960N(Korean set) after I rooted it about a year ago. Few days ago I saw a new ver of Magisk(old ver 17.2 flashed w/TWRP) at Magisk manager and wanted to update but hesitate. I backup a few important file like whatsapp, SMS & contact list before I carry on further. Today I decided to update the Magisk and my fear was right, after it reboot my Note 9 stuck at "Samsung" logo. I let it there initially and after a while it remains at same place. I tried to switch it off by press the power button but no response. It won't switch off after I tried, 10, 20 and 30 seconds. I found out there is a way to reboot it by holding "power + volume down". I successfully got it boot to recovery to TWRP.
I thought it maybe the Magisk was corruptted during update so I download the Magisk zip v19.3. Then I booted to TWRP and installed the Magisk zip. I reboot the Note 9 after Magisk installed. Again I was stuck at Samsung logo. I thought maybe the sequence was not correct; beside the Magisk there maybe need few more so I followed the root sequence(skip root); 1. Magisk 2. no-verity-opt-encrypt-6.0 3. RMM-State_Bypass_Mesa_v2
Same problem, I stuck at Samsung logo. As early problem, I couldn't switch it off by pressed the power switch. I have to reboot to TWRP and use its interface to power off the phone. I have new problem this time; once I pressed the power button to power on the phone, it will goes to TWRP straight away. Tried few times and it remain the same problem. The last action what i did is flashed a new TWRP v3.3.1-0-crownlte and it didn't help either.
My Note 9 has 2 problems;
1. go to TWRP recovery straight after press power button to power up the phone.
2. stuck at samsung logo after user TWRP to reboot.
There is one more thing I didn't pay attention previously, the "mount" in the TWRP what is supposed to mount? It "mount" the SD card when it last to flash zip files.
Appreciated anyone can helps, thanks.

Try to flash different kernel. Then flash magisk again. Although I doubt it could help, but your phone has bricked already, so worth to try.

If it's really brick, I'll consider to flash it "pie" since my one still "oreo". Any chance just reflash it with oreo again with odin but retain data?

user109 said:
If it's really brick, I'll consider to flash it "pie" since my one still "oreo". Any chance just reflash it with oreo again with odin but retain data?
Click to expand...
Click to collapse
Phone will factory reset after flash stock regardless odin or smartswitch. Of course you can still flash oreo. But flashing stock should be the last resort.

Rosli59564 said:
Try to flash different kernel. Then flash magisk again. Although I doubt it could help, but your phone has bricked already, so worth to try.
Click to expand...
Click to collapse
You did mention to flash a different kernel, what will it be the most suitable?

I found a suggested solution to try; flash(with oreo, same ver) with odin and check files except at CSC section choose "home_csc" instead normal "csc". Reflash was succeeded, in a way.. It did break something though.. My note 9 is able to boot normal but was stopped at lock screen(pattern lock) which I was set to lock my phone. Now it's lock screen loop even though I draw the pattern correctly. It just refuses to unlock. I use Samsung "findmymobile" try to unlock it and unsuccessful; the app cannot find the phone. It prompted "offline"! It's strange, I can see my carrier and wifi are working. I can call the preset emergency numbers to call. I used another phone to call and it can receive the call. It can receive whatsapp message. I tried google and it works. The google app is able to find my phone. I have no idea why my samsung account won't work. Now I'm clueless.. :crying:

user109 said:
I found a suggested solution to try; flash(with oreo, same ver) with odin and check files except at CSC section choose "home_csc" instead normal "csc". Reflash was succeeded, in a way.. It did break something though.. My note 9 is able to boot normal but was stopped at lock screen(pattern lock) which I was set to lock my phone. Now it's lock screen loop even though I draw the pattern correctly. It just refuses to unlock. I use Samsung "findmymobile" try to unlock it and unsuccessful; the app cannot find the phone. It prompted "offline"! It's strange, I can see my carrier and wifi are working. I can call the preset emergency numbers to call. I used another phone to call and it can receive the call. It can receive whatsapp message. I tried google and it works. The google app is able to find my phone. I have no idea why my samsung account won't work. Now I'm clueless.. :crying:
Click to expand...
Click to collapse
it's a Samsung stupid lock as your Note 9 has not fully booted you will not be able to find it via my Samsung.. There is a bug even if you draw the correct pattern the phone will not unlock it's a bug this has been covered when the Note first came out as the first or second update caused this issue! i did read somewhere there is a way around it, but this was a year or so ago you need to check Samsung official forums for the pattern bug fix check Samsung forums USA it has been covered in-depth over there!

N1NJATH3ORY said:
it's a Samsung stupid lock as your Note 9 has not fully booted you will not be able to find it via my Samsung.. There is a bug even if you draw the correct pattern the phone will not unlock it's a bug this has been covered when the Note first came out as the first or second update caused this issue! i did read somewhere there is a way around it, but this was a year or so ago you need to check Samsung official forums for the pattern bug fix check Samsung forums USA it has been covered in-depth over there!
Click to expand...
Click to collapse
Hi N1NJATH3ORY, I did google around the screenlock loop problems and most of them done with 1) simple reboot 2) boot to safe mode 3) use "samsung "findmymobile". A most common solution; "wipe". A few issues raised at Samsung forum but not helpful; "call Samsung support".. There was an interesting article which suggested the problem is from google itself. Here is the link; https://www.androidpolice.com/2019/12/12/google-pixel-pin-lock-screen-loop-help/
"If the encryption of the "Synthetic Password Key blob", which needs to be decrypted in order for the unlock process to be resolved, is not able to retrieve a stored decryption key if it was corrupted." from the article. I'm not sure if this is the cause but from logic point of view it's possible. I believe the bloody Samsung knew this problem since day one but because it's not a"common" issue Samsung just swipe under the carpet.
What I did on my note 9 last action was reflash the oreo, if in the process of flashing the "Synthetic Password Key blob" has been wiped out then it may explain this screenlock loop problem, which I hope not to happen. I'll be screwed if it did. :crying:
I'll wait its battery to drain out to see what happen even though I doubt if any change..

As expected, the drained out of battery did not help, my note 9 remains locked. The only way is to try out new method and with high risk which will wipe out my data. Fortunately the new method work! Not only it overwrite the lock screen loop and also disable the google device lock.(One of the method I tried during my lockscreen loop which is useless. It creates an extra problem on top of the problem) I got all my data intact and allow me to do all backup. :highfive:

summary: update Magisk is not a full proof. The risk is 50% it will brick the phone. My advise is to backup every dan internal data before finger press the Magisk "update" especially it remaps the image! Manager APK is okay to update. I learned from the hard way and almost lost the whole dan data in my Note. You have been warned!

Gdhhs

Rooting Note8 SM-N950U with Nougat 7.1.1

Specs:
T-Mobile-locked Samsung Galaxy Note 8 - N950U
Baseband version: N950USQU1AQI5
Build number: NMF26X.N950USQU1AQI5
Android version: 7.1.1
Samsung Experience version: 8.5
Knox version: 2.9
I recently purchased the above Note8. I have bookmarked a root method[1], but it requires bootloader v7. If I'm decoding my phone's baseband version correctly, its on v1, so probably won't work with this method.
I'm wondering, if I let it do an OTA update to Oreo (Android v8), will it hit the requisite v7 bootloader so I can, according to the instructions on that page, flash it back to a pre-rooted Nougat? ( If there's a better method than what I'm planning to follow, please advise. I'm all ears! )
[1] www (dot) the custom droid (dot) com/root-galaxy-note-8-snapdragon-n950u/

Just stay on firmware you are on and use the old Samfail root method
Sent from my SM-N960U using Tapatalk

Thanks, butchieboy. Would this be the process for this phone?
https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340

Yes [emoji106] The thread is closed but you should still be able to get the files you need. If not I still have them and when I find time I could send them to you with Mega...but you still should be able to get them from the thread.
Sent from my SM-N975U using Tapatalk

The links are still good in that post, but I'm a bit concerned about them. The SamFAIL downloads for the v1 bootloader are designated for N950F ("for the Samsung Galaxy Note 8(SM-N950F)"), which is the European firmware. Mine's N950U (US).
Does this SamFAIL root actually rely on the European firmware? How does that impact the Snapdragon? I thought the European phones/firmwares were designed for a different processor.

No dice
I followed the instructions on that post to the letter. The first flash didn't cause my phone to reboot (as the instructions say it will), so I rebooted it myself and got it back to the "Emergency" screen, whereupon I did the part #2 flash. It reset that time, and now it's stuck in an "Installing update" loop with the Android icon (with a "warning" icon above it) just appearing over and over.
What do I do now? Do I have to try and flash a stock ROM and see if I can recover the phone? Or is there something I can do from here that will help it continue?

Boot to recovery and factory reset
Sent from my SM-N975U using Tapatalk

And the angels sang!
Since I couldn't get the damn thing to shut off anyway, I left the phone in the "Installing" loop overnight (since that was the least risk of screen burn). This morning, the device was dead because the battery had drained to zero, so I put it on the charger. I left it there for only about 30 minutes so it had just enough juice for me to try and get it into recovery mode.
I must not have held the buttons correctly, because it went into a normal boot instead of going into Download or Recovery. I let it go, intending to just try again once it entered the "Installing" loop, and LO! the "SAMSUNG" logo came up. It hadn't done that before. I put the phone aside and didn't touch anything while the logo pulsated, and it eventaully dropped into the setup screen! :victory: Of course, it almost immediately shut down because the battery hadn't charged enough, but I think it somehow reset/corrected itself when it lost all power overnight.
I left it on the charger and monitored the level. It stopped increasing at 80%, which is the expected behavior with this solution. I powered it on again, and everything is as described in the rooting post (except that SuperSU did not prompt me multiple times to update it).
So, at this point, I'd say I'm good. Looks like it reset itself, and the root succeeded. Hopefully anybody coming along later with this same issue on the Note 8 will see this post.
Thanks again, butchieboy.