I tried to root stock Oreo T-Mobile, but got stuck with the T-Mobile splash screen.
Eventually flashed stock Nougat and then OCX27, but now Wi-Fi and IMEI are lost, phone can't read SIM card.
Baseband shows as unknown in settings.
Is there any way to fix it?
Hey i got the same problem, testing a ROM in Development. I flashed a OREO FlashALL, when i rebooted, no wifi no signal, mac address is like 02.00.00.00.00, Not sure hold to go about fixing it. I have another device on the way but i still would like to figure out what happen...
---------- Post added at 08:59 PM ---------- Previous post was at 08:33 PM ----------
Try flashing the complete firmware i just found in the thread : https://androidfilehost.com/?fid=746010030569947760
---------- Post added at 09:00 PM ---------- Previous post was at 08:59 PM ----------
Try flashing the complete firmware i just found in the thread : https://androidfilehost.com/?fid=746010030569947760
Thanks. Tried all of those and they didn't work. Ended up getting a replacement
What root method did you use? I rooted mine with magisk with no issue. Also stock t-mobile oreo.
Related
Does anyone know where I could find an image of the stock L520VPUANA7 ROM? I can't find it on sammobile or samsung-updates. Or does anyone at least know when it is expected to be released?
Basically, I had updated to NA7 for the wi-fi calling, decided I didn't actually need it, and tried to downgrade to the MK2 version so I have a rooted device. However, it turns out that some idiot at samsung decided to make attempting to flash an older, official stock ROM not allowed and therefore the device should stop working and not boot. I can turn my phone on, and the Samsung Galaxy S4 Mini logo shows up for half a second, but immediately after that I get the error about
"Image size too large! W:1080 H:1920
display image fail
SECURE FAIL: KERNEL"
I can still boot to the odin download screen, and I have attempted flashing various different kernels and bootloaders, etc. but nothing works. I am assuming that if I could flash the official NA7 firmware, then it would work again since that would make all the KNOX stuff happy.
Also, a side note for anyone that is interested, the KNOX values shown on the odin screen got set to 0xfffffffc (-4), not to 0x1 like most other people have seen. Does that mean anything special?
yes you can but.
yeah you can but wich kernels have u tried before meaby for flash bad kernel now is giving you problems you should be carefull if the jkernle that you flash is for your phone! i will find out about some fix for you let me see!:good::fingers-crossed:
Same Boat
Hopefully someone can get this quickly im in the same boat....shouldnt have taken the OTA Update...
Has anybody get a copy of these ODIN? i softbricked too
---------- Post added at 10:23 PM ---------- Previous post was at 10:07 PM ----------
In fact i have another L520 working, is there a way i can extract stock rom off that phone?
snoop1979 said:
Has anybody get a copy of these ODIN? i softbricked too
---------- Post added at 10:23 PM ---------- Previous post was at 10:07 PM ----------
In fact i have another L520 working, is there a way i can extract stock rom off that phone?
Click to expand...
Click to collapse
I'm stuck too,I need to get my phone back alive.anyone has the stock image.please share it.
NA7 is now available on samsung-updates.
Phone is rooted, used the gsii-repair from play store. Says
'nv_data.bak and his md5 files canceled'
I need help here and I'm having little luck. When I hit *#06# it shows me imei no problem but refuses to see Sim card.
Sent from my Nexus 5 using XDA Free mobile app
Well, I'm not sure about that app....but the dev even stated use at your own risk. However, you could see if they have a website or anything for help.
That said. Have you tried Odin to return to stock....and see if you still have issues???
If you want to try it, here's a guide. Links in OP are dead, but post 5 has some mirrors. Failing that, go to last page and read back to see if there are other links.
http://forum.xda-developers.com/showthread.php?t=2226886
Good luck!! ?
---------- Post added at 09:59 PM ---------- Previous post was at 09:59 PM ----------
Oh....an obvious question.... Did you try a new SIM?
I have a Reach through Boost. Nice phone except for storage issues. Currently running 5.1.1. Unlike other Kyoceras it has a developer's option to allow unlocking of bootloader. Does anyone know how to root and if there is a Android 6 rom that can be used with the Reach.
You have to go into developer mode and check OEM Unlock. KingRoot did the trick for me after that.
Is that all? Cuz it didn't change a dang thing for me, bro.
Sent from my C6743 using XDA Free mobile app
aces5150 said:
You have to go into developer mode and check OEM Unlock. KingRoot did the trick for me after that.
Click to expand...
Click to collapse
I check OEM unlock and authorized debugging and still nothing seems to be working for me. did you do anything else for your C6743
root
Kilparis87 said:
I check OEM unlock and authorized debugging and still nothing seems to be working for me. did you do anything else for your C6743
Click to expand...
Click to collapse
swicth homes bc found security in it it will lock till reset unless other wise
What do u mean by switch homes?
Yeah I can't get this phone rooted. I've taken days researching. Nothing.
I enabled OEM unlocking, installed Kingroot 5.2.1, and was able to achieve root on first try.
---------- Post added at 06:29 PM ---------- Previous post was at 06:23 PM ----------
Oops, spoke too soon, says in Kingroot, this model restricts ROOT authorization, even though it says it gained root successfully... so wtf then how did you get root if its restricted?? Tha Fuuu..
Took me like 6 times, restarting my phone after each time. Kingsroot 5.2.1
360root
activate phone
download system update
360root
root
phone reboots
root again
etc
just temp root
wait a few days
??
---------- Post added at 03:04 AM ---------- Previous post was at 02:59 AM ----------
Ggggg
successful root
I have managed to give root access to my Kyocera Hydro Reach with PermRoot in its latest version
wow
Arguzhan said:
I have managed to give root access to my Kyocera Hydro Reach with PermRoot in its latest version
Click to expand...
Click to collapse
mine was, but the company keeps blocking it and lucky patcher, i still use the phone for wi-fi but has no connection with any carriers, if you find a recovery or rom id like to have it, plus id like to connect it to my 32bit tablot if you have links to software, its not compatiable with my windows 8.1
Root Kyocera c6743
Kingroot roots device but root checker finds no root privileges...several subsequent attempts using same app actually began requesting superuser access, but eventually produced no joy all scenarios
---------- Post added at 11:13 AM ---------- Previous post was at 10:57 AM ----------
As I stated kingroot will do the job but it seems to be ONLY a temp root...grrrrr. will check adb/fastboot for manual solution
that's a nice phone, its not write/ can't be rooted, damages the core, I had (0)
---------- Post added at 03:34 PM ---------- Previous post was at 03:31 PM ----------
lexcin said:
that's a nice phone, its not write/ can't be rooted, damages the core, I had (0)
Click to expand...
Click to collapse
does anyone know how to use kitchen, I don't have a good p.c right-off hand, I need a custom recovery...
thanks
I was thinking of something so I'll just quickly say it.
1. Kingroot Temp Root
2. CWM app?
3. Magisk Root
I don't know if this will work.
Edit: Yeah no doesn't work
I think you need to flash the phone with a pre-rooted stock rom
get msl code, enable usb
use kyocera flashing tool exe
stick majisk in the boot folder and flash ?
---------- Post added at 11:51 PM ---------- Previous post was at 11:46 PM ----------
the new kyocera hydro reach are patched and won't root had a factory boost a few months ago, and it was patched won't root at all
Research
So I'll try researching a way to root this device so I'll back if I find anything
had one a few Christmas ago, got all excited, the phone and the contract, the 3g went out a month or so later... and that was about it for me, these days I'm just using a cheap phone, with insurance or warranty, still takes a few weeks to replace... I'm trying the Blu mtk veiw 1 right now 25 bucks
So long story short I ****ed up. My device is currently in fastboot mode.
To sum everything up: My phone's camera wasn't working so I contacted OnePlus to RMA it and I wanted to factory reset and re-lock the bootloader before sending it back. Before locking the bootloader though I had been in developers options I disabled oem unlocking and adb debugging which was a huge mistake and I realize that probably screwed me over.
Now when I try booting my phone the OP logo shows for a second vibrates and turns off, I can't get into recovery and the same thing happens. I can't flash anything through fastboot because it tells me remote oem unlock disabled and either remote partition flash is denied when attempting to flash.
Please if anyone can help it would greatly be appreciated.
Try using one of the toolkits in development forum and see if you can reflash anything or try some of the other tools
---------- Post added at 01:23 AM ---------- Previous post was at 01:22 AM ----------
I'd use this one http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799 and I'd try option 12&13 if it were mine
---------- Post added at 01:28 AM ---------- Previous post was at 01:23 AM ----------
I'd also try this.
---------- Post added at 01:28 AM ---------- Previous post was at 01:28 AM ----------
[/COLOR]http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Jaymie1989 said:
Try using one of the toolkits in development forum and see if you can reflash anything or try some of the other tools
---------- Post added at 01:23 AM ---------- Previous post was at 01:22 AM ----------
I'd use this one http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799 and I'd try option 12&13 if it were mine
---------- Post added at 01:28 AM ---------- Previous post was at 01:23 AM ----------
I'd also try this.
---------- Post added at 01:28 AM ---------- Previous post was at 01:28 AM ----------
[/COLOR]http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
I have tried using the toolkits however since ADB and oem unlocking were disabled in the developer options prior I can't flash anything to my device without unlocking the boot loader, and I cant unlock the bootloader with enabling oem unlocking, and I can't boot in the device
I'd try this
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Another who wanted to relock.
Why???
Unlocking doesn't void the warranty !
When will people understand that?
Try the mega unbrick thread / tools, it should be enough, it's low level Qualcomm tools.
If no success call one plus tech service
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
Yep. This is why I immediately unlock the bootloader the minute I take my Nexus/OnePlus devices out of the box, even if I don't plan on rooting/flashing custom ROMs. Even botched OEM software updates can brick these phones.
Striatum_bdr said:
Another who wanted to relock.
Why???
Unlocking doesn't void the warranty !
When will people understand that?
Try the mega unbrick thread / tools, it should be enough, it's low level Qualcomm tools.
If no success call one plus tech service
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
Click to expand...
Click to collapse
i don't think they will, so many people do this, there is absolutely no reason to relock the bootloader on the Oneplus 3 since it does not void warranty and most insurance companies accept this as well, this is not Samsung, HTC, LG, Motorola, or any other "flashship phone".
PEOPLE AGAIN YOU DO NOT HAVE TO RE-LOCK YOUR BOOTLOADER, THERE IS NOT REASON WHATSO EVER TO NEED TO!!!!
To the OP if you plan on returning it, does not matter if u are stuck in fastboot mode, i am sure they won't care since they know how to easily fix it anyway, so just go with ur normal return, if u plan to keep it there are threads on here on how to fix as some posted earlier in the thread
Hello all
A couple months back I bought what I thought was a Note 4 SM-910F it has had a problem sending SMS to any international prefix number e.g +33 and connectivity here in UK on EE is not amazing.
I did some investigation using CPUz and discovered it is an SM910V - even though 'About Phone' reports it as an SM910F
the ebay seller has disappeared, so I am stuck with it
Cpu-z reports it jas a Verizon SM-910V bootloader with the OS (5.0.1) for an SM-910F
Bootloader: N910VVRU2BOG5
Build UD:LRX22C:N910FXXU2COC6
Kernel version. N910FXXU2COC6
SO: I tried flashing stock 5.1.1 for SM910V using Odin and now have the dreaded Verizon Software Assistant - soft brick
What I have tried already
I have read that the VZW software won't install if you don't have a working VZW phone - I've tried and it does not install for me on either Mac or PC
Smart Switch/Kies Emergency software recovery and initialization" option does not work
What are my options?
Any ideas what I can do to get phone at least working again?
1. re try Stock restore B0G5? with ODIN
2. Something with a PIT file - but which PIT file?
3. Catch a flight to the USA and go to a Verizon store to get it reset?
any help much appreciated
http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
---------- Post added at 10:55 AM ---------- Previous post was at 10:52 AM ----------
Download and flash with odin. https://www.androidfilehost.com/?fid=24052804347793292
If it doesnt work id flash the bpa1 fullfirmware and unlock the bootloaded.
---------- Post added at 10:56 AM ---------- Previous post was at 10:55 AM ----------
Extraxt the file with 7zip. Use odin plce in ap slot and Use pitfile from thread at the bottom of th post. Goodluck
codydixon-LEGEND
Thank you so much... Cody
Just flashed the Pit file at the bottom of the post using the Pit button in Odin 3.11
Reboots perfectly:highfive:
Now back to Verizon setup:victory: