After a failed root attempt on my SM-N920L I have lost network capabilities; there is no baseband and imei.
The phone was working perfectly until the root attempt-- which was made by flashing a file named "Noble-Kernel-N920L_Alpha1.tar" which caused a "Kernel is not Seandroid Enforcing" error and temporarily bricked the phone.
After some googling I was able to fix the bricked phone, but the network problem started to occur at this point.
I've since been able to successfully root the phone using the method on this site and everything else with the phone is working perfectly. (From my experience with this particular model, SM-N920L, flashing "CF-Auto-Root-nobleltelgt-nobleltelgt-smn920l.tar.md5" is the only method that successfully rooted the phone.)
I have tried everything I could google to fix the problem:
-using a different sim card (and this sim card works fine on other phones)
- using the keypad method to punch in *#197328640# or other variants
-factory resetting
-downloading and installing stock rom using odin and also
-resetting by installing ap along with bl, cp, csc, even pti
-using twrp to wipe out (hopefully reset) everything
Obviously the imei is on the back of the phone, so there must be some way to salvage it somehow and enter it into the phone again but I am out of ideas. Any suggestions would be appreciated!
One side note:
Using twrp, I did try attempting to install two custom roms (AryaMod and Hyperdrive) to see if that would solve the problem. Everything installs fine, but once I get into the rebooting stage the screen turns off and does not turn on again-- nothing happens even though I wait for over 30 minutes. I just end up having to install the stock rom again. So I can't tell if installing a custom rom would solve the issue (someone on another forum was mentioning this worked for them). Any input on why the custom roms install fine, but then does not open during reboot, would also be appreciated!
update: I have successfully installed a custom rom-- installing seems to have worked after flashing this kernel: NEMESIS_KERNEL_N5_V2.0.zip instead of using the stock kernel.
But sort of as expected, installing the custom rom did not solve the issue.
"dr.ketan" mentioned in one of his threads about entering a bunch of codes using root explorer and Terminal emulator, but these methods also did not work.
sskkambad said:
update: I have successfully installed a custom rom-- installing seems to have worked after flashing this kernel: NEMESIS_KERNEL_N5_V2.0.zip instead of using the stock kernel.
But sort of as expected, installing the custom rom did not solve the issue.
"dr.ketan" mentioned in one of his threads about entering a bunch of codes using root explorer and Terminal emulator, but these methods also did not work.
Click to expand...
Click to collapse
Did your problem solved? I have the same problem with an endless rebooting. Sigh~
Related
Hello,
I own an Xperia Z C6603 and i was running the latest oficially available firmware before
i m quite new to all the stuff regarding flashing/rooting/unlocking etc
so today i decided to give it a shot.
now my phone is in a state that i cant use it any more.
Basically what i wanted to do is install this [BeanStalk-4.4015] custom rom. Now its stuck on the loadscreen forever.
I started with rooting the device following the description in one of the posts i found here (flashing the previous kernel with flashtool then rooting it and flashing the original latest kernel again) which worked out very well.
After that i unlocked the bootloader following another guide here in forums which went ok without any problems aswell.
As it seemed like it reset all my settings after unlocking the bootloader i reenabled the developer mode to set the USB debugging and security options for unofficial software aswell.
All went fine and i was preparing to install the custom rom so i put the zip file on my sd card entered the recovery mode and flashed the rom zip file.
It seemed all ok and the phone was restarting and its stuck in the boot screen ever since that. I tried to get it back in order by trying out various stuff i could find here on forums.
when i tried to reset the delvik cache initially i did not see any error messages or anything so i assumed that its done correctly also cleared the other caches which were listed. I was getting a bunch of errors but i assumed its because the folders could be empty as it seemed like the phone was completely reset after the bootloader unlock.
I could not get anywhere with the CWM recovery mode so i flashed MOEW kernel through flashtool. The meow kernel was mentioned in the post regarding the custom rom as viable and it included TWRP recovery so i wanted to give it a try.
First exactly the same happened when i tried to boot it normally... Stuck...
So after that i tried to mess around with the TWRP recovery which seemed a bit more complicated than CWM.
First that came to my eye was that i could not enable all the partitions (system was constantly disabled) i managed to enable it after hitting the fix permissions button a bunch of times also i started to get some error messages while trying to reset dalvik cache but none of this changed the main problem at all.
Also i m unable to access the SD card from my computer for some reason even if i enable USB teathering in CWM or TWRP.
any suggestions how to get the phone back to work ?
druvisk said:
Hello,
I own an Xperia Z C6603 and i was running the latest oficially available firmware before
i m quite new to all the stuff regarding flashing/rooting/unlocking etc
so today i decided to give it a shot.
now my phone is in a state that i cant use it any more.
Basically what i wanted to do is install this [BeanStalk-4.4015] custom rom. Now its stuck on the loadscreen forever.
I started with rooting the device following the description in one of the posts i found here (flashing the previous kernel with flashtool then rooting it and flashing the original latest kernel again) which worked out very well.
After that i unlocked the bootloader following another guide here in forums which went ok without any problems aswell.
As it seemed like it reset all my settings after unlocking the bootloader i reenabled the developer mode to set the USB debugging and security options for unofficial software aswell.
All went fine and i was preparing to install the custom rom so i put the zip file on my sd card entered the recovery mode and flashed the rom zip file.
It seemed all ok and the phone was restarting and its stuck in the boot screen ever since that. I tried to get it back in order by trying out various stuff i could find here on forums.
when i tried to reset the delvik cache initially i did not see any error messages or anything so i assumed that its done correctly also cleared the other caches which were listed. I was getting a bunch of errors but i assumed its because the folders could be empty as it seemed like the phone was completely reset after the bootloader unlock.
I could not get anywhere with the CWM recovery mode so i flashed MOEW kernel through flashtool. The meow kernel was mentioned in the post regarding the custom rom as viable and it included TWRP recovery so i wanted to give it a try.
First exactly the same happened when i tried to boot it normally... Stuck...
So after that i tried to mess around with the TWRP recovery which seemed a bit more complicated than CWM.
First that came to my eye was that i could not enable all the partitions (system was constantly disabled) i managed to enable it after hitting the fix permissions button a bunch of times also i started to get some error messages while trying to reset dalvik cache but none of this changed the main problem at all.
Also i m unable to access the SD card from my computer for some reason even if i enable USB teathering in CWM or TWRP.
any suggestions how to get the phone back to work ?
Click to expand...
Click to collapse
hey if you wana go back to stock rom follow this post forum.xda-developers.com/showthread.php?t=2240614
i think u have to fastboot and flash boot.img
try pacman rom which is better and bug free rom
Hi, are you still able to connect to flashtool in flashmode? If so have you tried to flash back to stock rom?
Check this thread out, it contains good stuff.... 3rd video show how to flash stock ....
http://forum.xda-developers.com/showthread.php?t=2275632
Good luck !!
Hello,
thx for your replies i m still able to access all the modes it just does not load up if i dont do anything
after i unlock the bootloader to i need to reroot the phone ?
as it seems right now to me it simply doesnt write anything when i try to flash the rom also some partitions are not available
Hello,
i managed to unbrick the phone using this tutorial http://forum.xda-developers.com/showthread.php?t=2458530
however i tried to redo all the steps following the guide to install the beanstalk rom and noticed that i m getting an error about updater package when i try to execute the installation from TWRP any ideas ?
would you suggest trying another 4.4 based rom ?
Hello again,
ok so i gave up on the beanstalk 4.4 rom and decided to try my luck with pac rom mtayabkk suggested
so now the problem is not as big as it was.
Able to get the rom to run however i m unable to import my contacts/sms/call log using titan backup
The restore seems to work but after that i m getting com.android phone has stopped error everywhere i go on my phone (the contacts/etc are actually restored in this process tho and work fine apart from the errors)
i did restore a bunch of other settings together with the contacts aswell which i found as safe to back up in a guide i found
so can you give me an advice how to properly restore this to the newest pac man rom and avoiding various errors after that ?
ps
i moved all my media to sd card so it does not concern me the only thing i cant seem to be able to move over apart from contacts/sms/call log are the APN settings which is bothering me a bit aswell as i can not receive the configuration messages from carrier but i found them on the internet and i will add them manually
trying to restore the stock backup from PC companion right now to export them again as i lost the backup in process of trying to deal with the error i was getting
would you suggest trying again with titan backup or any other tools ?
I updated stock rom by flashing to CWM 11. It worked out, but there were internet problems. So I then tried to flash 10.2 in recovery but when choosing a zip file I get "can't mound /sdcard/". So I that point I wiped data and then when phone boots it gave me message about encryption unsuccessful and that it needed to do factory reset. But factory reset does not work because there is an issue I think with the file system or formatting and it refers to errors with android_secure. I have tried everything. I have tried various recovery apps. I have tried flashing other roms with sideload but that does not work (even though adb makes a connection to the phone - I get some error about protocol fault). Any ideas how to unbrick this thing?
Forgot to mention that after the encryption unsuccessful nonsense, I flashed stock kernel. So maybe that is the issue? I have a JB kernel that I flashed after the 11 rom flash? Also, Kies will not connect to the phone. Odin connects fine. At this point I just want to flash stock rom but all the sites with downloads limit to very slow download and because my internet connection drops now and then those downloads fail. What a mess I got myself in...
thanks,
Brian
So I flashed a stock rom and it booted up, but now it shows baseband:xxxx and there is no mobile internet. Internet worked fine when I first went from stock rom to cyanogen 11 and I know I am in a location where there is internet. I have tried flashing various modem files for my phone and have read numerous posts about this issue, but nothing is working. Does anyone have other ideas? What I am expecting to see is baseband xxamg4.
Kind Regards,
Brian
So I've rooted my Z3c using dual recovery method, and later on flashed the Rectify mod, and everything seemed to be working well until I wanted to flash a file in recovery (I know I had CWM working at one point) but it is not working. I found the little NDR tool in the Rectify mod and tired the various recovery options (previously I would just use up on volume key). Well this is when I started noticing it not working and so I tried the manual volume key approach and still it is not working. I installed busy box and have found that can sometimes cause problems with NDR/Recovery however I attempted to uninstall was going to try different location but that's broken now too... I think.
So anyway, my problem is, if I re-install DualRecovery it still does not go to recovery.
Please help me get to Recovery mode so I can reflash rom.
Thank You
Have you installed a different busybox, most others aren't compatible with XZDR and will cause this kind of issue.
I'll tell you what I did, I downgraded firmware using flashtool, followed the dualboot method to upgrade while re-rooting and confirming recovery along the way (this seems to work) then as soon as I install rectify (making sure to flash dualboot flashable zip file before reboot) I'm no longer able to access recovery, not manually or using NDR. I also didn't intall busybox yet.
Oh boy what now, I'm back to square one.
I'm an idiot, what's the rectify mod? Point me to a download link and I'll see if there's something in it that's causing issues with XZDR.
Edit : I see its rectify rom. Well it most likely includes it's own version of busybox, hence the issue.
Hello. I'm posting here because I simply have no idea what to do about this... Here's the story:
Issue
-Fingerprint Scanner does not work. "error has occurred with the fingerprint sensor"
-Horrible lag occurs every 3 seconds. This will stop the phone for a second or so no matter what is going on. I could be typing, navigating menus, or scrolling.
I recently noticed In stock recovery it shows this at the bottom of the screen: "dm-verity verification failed..."
I have no idea what that means or if it's related to my issue.
What I've tried
-Factory reset / cache wipe in stock rom and recovery. FAIL
-Full odin restore of DOK2 firmware FAIL
-TWRP and wiping everything and all storage FAIL
-TWRP x3 wiping of everything just to be sure FAIL
-Flashing stock DOK2 in the form of zip file FAIL
-Fixing permissions in TWRP on stock DOK2 and on several different roms FAIL
-Flashing several different TouchWiz roms FAIL
-Freezing fingerprints.apk FAIL
About my phone
Firmware: N910TUVU2DOK2 sammobile com/firmwares/download/61414/N910TUVU2DOK2_N910TTMB2DOK2_TMB/[/url]
Baseband: N910TUVU2DOK2
Android version: 5.1.1
Model: SM-N910T
Carrier: T-MOBILE
Buildnumber: LMY47X.N910TUVU2DOK2
TWRP versions tried
2.8.7.0
3.0.0-1
Odin versions tried
3.07
3.09
3.10.7
Useful information and discoveries
CM/AOSP based roms
I got this to work. The phone will not have any lag at all... but here's the issue. I have a samsung galaxy gear S smartwatch so I require a samsung rom and gear manager to make everything work properly. I simply can't use (and don't want to use) any rom that is not touchwiz based.
This issue started after:
- I got a replacement warranty phone and restored the old rom I was using from my last Galaxy Note 4 using TWRP
- I booted the old system (which had no fingerprints stored or even used.
My situation
I need to get this phone to work and I don't think I have it under warranty anymore.. This is the 3rd note 4 and my last note 4 had a similar issue.
I've searched for hours in this forum trying to figure out this issue. I'm totally lost at this point. Please let me know what I can do. That would be very very helpful.
By fall do you mean... Failed to resolve the problem... Or failed to do the particular procedure?
freeza said:
By fall do you mean... Failed to resolve the problem... Or failed to do the particular procedure?
Click to expand...
Click to collapse
Sorry for not clarifying. It failed to solve the fingerprint sensor error or the lag issues.
Have you tried to format everything in twrp?
Format everything at least 3 times, flash a rom and see if that helped.
mistamikel said:
Have you tried to format everything in twrp?
Format everything at least 3 times, flash a rom and see if that helped.
Click to expand...
Click to collapse
Yes. I've tried all methods of formatting (including "format data" option and also formatting each partition that I could to ext4) no luck with the fingerprint or lag issue.
Do you know where on earth the culprit files/configurations exist ?
I am having the same issue and as far as i can say, its a faulty fingerprint driver for installation or maybe our faulty phones are installing Thema wrong. For the w8...you can install the Puerto Rico official Rom Form dec 15. I couldnt find any solution for the 910f.
I am having the very same lag issue as we speak. I've tried everything also, but the only AOKP rom I flashed was CMRemix, and that's when I started to have this problem. I'm at a loss trying to figure this annoying problem out. Which AOKP roms did you flash that worked perfectly for you, and which kernel were you using? I've also tried different kernel/rom combo's also, but with no luck.
Sent from my SM-N910T using XDA Premium HD app
Hey guys,
I know I know, I was stupid to try to get this working but I tried and failed. Now I'm just looking to get my old phone back and just leave it at being rooted (with custom recovery installed) and a custom rom. All 3 of these I had successfully done before I installed the framework zip which is where the problems arose.
I'll give you as much information as possible:
Phone: SM-G935F (UK version and on EE network)
Rooted with: CF-Auto-Root-hero2lte-hero2ltexx-smg935f
Custom Recovery flashed: twrp-3.0.2-2-hero2lte.img.tar
Other things flashed: UPDATE-SuperSU-v2.76-20160630161323.zip
no-verity-opt-encrypt.zip
Custom Rom flashed: KryxxOS-R1.3-G935F.zip
All of these were working and I should have stopped here but with the new Pokemon craze I really wanted Xposed installed to use the modules for it however massively regret it. I wish to get back to this point.
Zip used for Xposed: xposed-v86-sdk23-arm64.zip
Phone initially wouldn't do anything apart from show a battery (not charging (grey icon with lightening in it)) icon when connected to power. And it would ONLY do something when booting into download mode allowing me to go into it. It seemed the custom recovery was no longer working. I then tried everything, flashing back all Stock firmware for my model using ODIN and correct files for my phone (G935FXXU1APF2_G935FEVR1APE2_EVR), that didn't work. Even when installing only AP, all 4 using first HOME_CSC in the CSC and then using all 4 using the CSC file in the CSC. Then I tried using Smart Switch's recovery system, this failed also. Then I remembered hmmm, I can try to reflash my custom recovery using Odin. That WORKED. I thought great now I can do something and sure enough I could wipe my phone and access my files on my phone again when rebooted. After the reboot I tried just re-flashing the SU, the no-verify and the custom ROM thinking it would take me back. It still didn't boot. Black screen nothing. The last thing I attempted was to flash the Xposed Framework uninstaller and used this zip : xposed-uninstaller-20150831-arm64. I didn't know what this asci files were so I didn't flash them? After flashing the uninstaller, I again flashed SU, no-verify and the custom ROM. Nothing. Still nothing. However...whilst I was typing this, because my phone was connected to my PC and not stuck in DL mode or anything, it's now randomly come up with a battery charge. 3% so far but I want to wait until its higher before I risk trying to turn it on. Could it have been a dead battery all along whilst trying to fix?
I'd appreciate your help even if its to clarify that the battery seems to be the problem. I'll keep you posted with it throughout the night but if it gets sorted tonight it means I don't have to go into the city tomorrow to buy a fix. Thanks to all who post. Ask if you need anymore information.
Chris
hey, how did things go now, is it back to normal... rooted with TWRP and your custom ROM of choice ?
nexiros said:
Hey guys,
Chris
Click to expand...
Click to collapse
lol i know this is an old post but damn what a mess you are. you did just everything wrong. :laugh::laugh: hope everything is back working now