[Q] New phone keeps crashing at initial set-up - One (M7) Q&A, Help & Troubleshooting

Hi everyone,
I was so glad when I finally received my HTC One today. Things went a little less awesome when I realised that I couldn't possibly make it to the end of the initial set up without it crashing and rebooting.
In other words, as soon as I unlock it (or after a few steps of the initial set up process), it crashes and just reboots.
What I've tried so far :
- Factory reset : doesn't change anything
- RUU : gives me a splendid error 131 - customer id error
- Flashing a stock ROM through recovery mode : recovery gives me a red triangle, I cannot do anything there
I don't really want to return it and have to wait for weeks to get it back hopefully fixed, yet I didn't try installing a custom ROM in case the problem would still be the same on another ROM and having no choice but to use my warranty.
If it might help, the CID of my phone is TMOB101.
I'm quite running out of ideas so any help would be very much appreciated
Thank you !

I finally unlocked bootloader, flashed custom recovery and the most up-to-date stock ROM available, but the problem is still the same.
So I flashed stock recovery back and re-locked bootloader, I guess I have no choice but to return it now since I'm pretty sure this is not a ROM-related issue. I just hope that they won't say it's my fault since I flashed another ROM and that my warranty will still work.

what exactly does it do? at which step does it fail? and do you get any error message or fc

skinsfanbdh said:
what exactly does it do? at which step does it fail? and do you get any error message or fc
Click to expand...
Click to collapse
Hi and thank you for your reply.
It doesn't crash at a particular step of the set-up, it just randomly crashes as soon as it's booted.
Generally, I unlock the phone (sometimes, even the fact of releasing the lock makes it crash), go through one or two steps and then it crashes.
Just to be clear, there is no FC. It just freezes and reboots.
The only error I get is the "Error report" notification when it has restarted.

what roms did you try so far

Umbraz said:
Hi and thank you for your reply.
It doesn't crash at a particular step of the set-up, it just randomly crashes as soon as it's booted.
Generally, I unlock the phone (sometimes, even the fact of releasing the lock makes it crash), go through one or two steps and then it crashes.
Just to be clear, there is no FC. It just freezes and reboots.
The only error I get is the "Error report" notification when it has restarted.
Click to expand...
Click to collapse
Sounds like a CPU binning issue to me, maybe you shouldn't have unlocked it

skinsfanbdh said:
what roms did you try so far
Click to expand...
Click to collapse
The odexed one from this thread. I did not try any custom ROM.
MacHackz said:
Sounds like a CPU binning issue to me, maybe you shouldn't have unlocked it
Click to expand...
Click to collapse
I didn't want to do that before I read this article which clearly states that unlocking the bootloader does not void the warranty.
So CPU binning issue it is ? What's weird is that I've searched this forum a long long time before making this thread and never found anything similar to my case...

Umbraz said:
The odexed one from this thread. I did not try any custom ROM.
I didn't want to do that before I read this article which clearly states that unlocking the bootloader does not void the warranty.
So CPU binning issue it is ? What's weird is that I've searched this forum a long long time before making this thread and never found anything similar to my case...
Click to expand...
Click to collapse
While that article is true, HTC does void warranty based on bootloader, and you would have to sue them to get your money back, paying legal fees...
It sounds like your voltage is too low and your CPU is shutting down. I would advise flashing ARHD rom (optimised stock) and Bulletproof kernel so that your voltages are the usual.

MacHackz said:
While that article is true, HTC does void warranty based on bootloader, and you would have to sue them to get your money back, paying legal fees...
It sounds like your voltage is too low and your CPU is shutting down. I would advise flashing ARHD rom (optimised stock) and Bulletproof kernel so that your voltages are the usual.
Click to expand...
Click to collapse
Ok, I'll try that, thanks. Is there a permanent fix to this if I'm able to get it working with your recommended stuff ?

Umbraz said:
Ok, I'll try that, thanks. Is there a permanent fix to this if I'm able to get it working with your recommended stuff ?
Click to expand...
Click to collapse
Yeah, try that first

MacHackz said:
Yeah, try that first
Click to expand...
Click to collapse
Just one thing, wouldn't it be even worse for my warranty if this doesn't work and they see I've flashed a custom ROM ?

Umbraz said:
Just one thing, wouldn't it be even worse for my warranty if this doesn't work and they see I've flashed a custom ROM ?
Click to expand...
Click to collapse
No because you can go back to stock actually, is there 'tampered' on your bootloader?

MacHackz said:
No because you can go back to stock actually, is there 'tampered' on your bootloader?
Click to expand...
Click to collapse
Yes there is. Tampered relocked.

Umbraz said:
Yes there is. Tampered relocked.
Click to expand...
Click to collapse
Yeah you should try what I suggested

MacHackz said:
Yeah you should try what I suggested
Click to expand...
Click to collapse
Yep, on it :fingers-crossed:

MacHackz said:
Yeah you should try what I suggested
Click to expand...
Click to collapse
Do I have to pick any particular tweak during the install ?

Umbraz said:
Do I have to pick any particular tweak during the install ?
Click to expand...
Click to collapse
No, just the SQL and build.prop

MacHackz said:
No, just the SQL and build.prop
Click to expand...
Click to collapse
Everything's installed, same problem though

Umbraz said:
Everything's installed, same problem though
Click to expand...
Click to collapse
maybe try a custom kernel that lets you choose the cpu voltages in aroma

skinsfanbdh said:
maybe try a custom kernel that lets you choose the cpu voltages in aroma
Click to expand...
Click to collapse
Hi skinsfanbdh, do you have any kernel suggestion ? And which voltage should I pick ?
Thanks

Related

[Q] HTC Desire C stuck during boot

Hi everyone,
Recently I tried to follow a post from xda dev on putting a new kernel on my HTC Desire C.
Although I followed all the steps I am now unable to get past the boot screen wit the htc logo.
I have tried a number of solutions to make it work but nothing so far, backup recovery failed, changing to another kernel failed.
I think that at this point it might be bricked, and all that I can see is the logo and a disclaimer message.
Does anyone has any idea if I could fix it, and what do I need to do?
Kind regards,
Florin
Edit: thanks to aashay960 for telling me how to fix this.
The solution was to reinstall kernel and rom (since I made a mess of it initially)
Current config : CyanogenMod 10 + N.O.P.E Kernel 875Mhz
sir_florin90 said:
Hi everyone,
Recently I tried to follow a post from xda dev on putting a new kernel on my HTC Desire C.
Although I followed all the steps I am now unable to get past the boot screen wit the htc logo.
I have tried a number of solutions to make it work but nothing so far, backup recovery failed, changing to another kernel failed.
I think that at this point it might be bricked, and all that I can see is the logo and a disclaimer message.
Does anyone has any idea if I could fix it, and what do I need to do?
Kind regards,
Florin
Click to expand...
Click to collapse
Its not bricked. Tell me which kernel you are trying, with which rom? And try flashing a lower frequency kernel.
aashay960 said:
Its not bricked. Tell me which kernel you are trying, with which rom? And try flashing a lower frequency kernel.
Click to expand...
Click to collapse
I tried the Prometheus Kernel for sense linked in your signature with the stock. I got to the HTC logo screen and it got stuck there. It might be that the method I used was wrong.
Would it be possible to use the ones you do? Cyanogem mode and the N.O.P.E Kernel?
Can I install them only with recovery? And is there and "xda approved" method of installing kernels and custom roms?
Thanks,
Florin
Flash a lower frequency Prometheus Sense Kernel from fastboot.
You cannot use nope for sense roms. Nope is for Jellybean roms only.
As of now we have two ways to flash a kernel on this device. One is fastboot, which I personally use. Second is the auto Boot.img flasher that you will find if you search..
For now, tell me what frequency you tried. And try a lower one.
aashay960 said:
Flash a lower frequency Prometheus Sense Kernel from fastboot.
You cannot use nope for sense roms. Nope is for Jellybean roms only.
As of now we have two ways to flash a kernel on this device. One is fastboot, which I personally use. Second is the auto Boot.img flasher that you will find if you search..
For now, tell me what frequency you tried. And try a lower one.
Click to expand...
Click to collapse
Hi, I forgot to mention in the previous one that I initially used the 816 one, and then switched to the lower one 767.
Is it worth it to try a "clean install" as in a new configuration with a new kernel and rom?
No a wipe is not necessary.
Just make sure you do
Fastboot erase cache
Fastboot flash boot boot.img
Try an even lower one.
Now that your bootloader is unlocked. Why not try a custom rom?
aashay960 said:
No a wipe is not necessary.
Just make sure you do
Fastboot erase cache
Fastboot flash boot boot.img
Try an even lower one.
Now that your bootloader is unlocked. Why not try a custom rom?
Click to expand...
Click to collapse
What rom do you have in mind? I was thinking about cyanogen
sir_florin90 said:
What rom do you have in mind? I was thinking about cyanogen
Click to expand...
Click to collapse
Yeah that seems to be the most popular rom around. Been using it for a long time..
You can look at other options too. You can't really go wrong with any...
Just make sure to flash nope kernel with a jb rom.
aashay960 said:
Yeah that seems to be the most popular rom around. Been using it for a long time..
You can look at other options too. You can't really go wrong with any...
Just make sure to flash nope kernel with a jb rom.
Click to expand...
Click to collapse
I have noticed: CyanogenMod 10 + N.O.P.E Kernel 875Mhz.
Is this for you desire C?
Yes that is..
aashay960 said:
Yes that is..
Click to expand...
Click to collapse
Thanks man, the phone is back alive. I was feeling so bad when I realised it might be bricked. Thanks again :d
Pls delete.
wilberfish said:
Pls delete.
Click to expand...
Click to collapse
Why would you ask a thread to be deleted without the consent of the OP
Sorry. My bad, I was referring to my post.
I seem to be having connection problems with the xda app resulting in posts when I thank people and only getting notification of successful posts when I am reading another thread!
Sorry for the confusion I caused.
wilberfish said:
Sorry. My bad, I was referring to my post.
I seem to be having connection problems with the xda app resulting in posts when I thank people and only getting notification of successful posts when I am reading another thread!
Sorry for the confusion I caused.
Click to expand...
Click to collapse
Oh its ok, I didnt get what you said. Some tips if you want someone to disregard your post just put a "Deleted." or "[Deleted]" tag.
OK. Thanks.

[Q] M& slowdown - factory reset ?

I'm experiencing some gradual slowdown with my M7 running Viper One 7, to the point where I'm clearing the caches once a week. Seems stoopit.
Since I've flashed prolly 20 ROMs over the last year, I'm thinking that it might be worthwhile to do a factory reset, wipe the SD and all.
If I make a Nandroid with TWRP and use that to start with, wouldn't that actually include any bad gris gris and therefore kind of null the point of doing the factory reset?
Would I be better off, after the factory reset, flashing the ROM and Kernel (EL-X) from scratch and dropping all else from a back-up?
Or am I over thinking this?
Something slowing my M7.
I have 140 apps. No games.
About a dozen of which are running normally, using 785mb of 1.7gb RAM.
And 27.5G of total storage used.
Wtf 140 apps? I got maybe 30.
metropical said:
If I make a Nandroid with TWRP and use that to start with, wouldn't that actually include any bad gris gris and therefore kind of null the point of doing the factory reset?
Click to expand...
Click to collapse
Probably but it might worth a try
Would I be better off, after the factory reset, flashing the ROM and Kernel (EL-X) from scratch and dropping all else from a back-up?
Click to expand...
Click to collapse
imo, yes it would be better to start over from scratch.
I have 140 apps. No games.
About a dozen of which are running normally, using 785mb of 1.7gb RAM.
Click to expand...
Click to collapse
shouldn't be an issue
And 27.5G of total storage used.
Click to expand...
Click to collapse
thats a lot, but I'm not sure its related to your issue.
Fairtex said:
Wtf 140 apps? I got maybe 30.
Click to expand...
Click to collapse
that's what I had when I bought my Sensation.
But stuff comes along ...........
alray said:
Probably but it might worth a try
imo, yes it would be better to start over from scratch.
shouldn't be an issue
thats a lot, but I'm not sure its related to your issue.
Click to expand...
Click to collapse
then away we go ......... from scratch
metropical said:
then away we go ......... from scratch
Click to expand...
Click to collapse
good luck, let me know if it worked
alray said:
good luck, let me know if it worked
Click to expand...
Click to collapse
no matter what I do, ViperOne remains as does the ElementalX kernel.
Weird
metropical said:
no matter what I do, ViperOne remains as does the ElementalX kernel.
Weird
Click to expand...
Click to collapse
what did you try ? Format Data in TWRP will completely erase the phone
then adb push a rom back to the phone and your off to a clean start
clsA said:
what did you try ? Format Data in TWRP will completely erase the phone
then adb push a rom back to the phone and your off to a clean start
Click to expand...
Click to collapse
thanks
http://forum.xda-developers.com/showpost.php?p=56964579&postcount=42028
metropical said:
thanks
http://forum.xda-developers.com/showpost.php?p=56964579&postcount=42028
Click to expand...
Click to collapse
so you have already done the Format Data ?
clsA said:
so you have already done the Format Data ?
Click to expand...
Click to collapse
I have . and in updating TWRP, I wiped the phone again.
so sideloading again.
ah well
so far, the couple apps that were misbehaving have been better.
but the 1 xPosed module I have, MacroExpansion isn't working correctly.
metropical said:
I have . and in updating TWRP, I wiped the phone again.
so sideloading again.
ah well
so far, the couple apps that were misbehaving have been better.
but the 1 xPosed module I have, MacroExpansion isn't working correctly.
Click to expand...
Click to collapse
The second you installed xPosed you screwed up in my opinion .. I have no use for it. But i understand many like it for the Sense 6 toolbox fuctions
alray said:
good luck, let me know if it worked
Click to expand...
Click to collapse
so far so good. found 1 offending app that slowed others, so it's gone.
seems to be back to what I remember.

No homescreen after root.

1.st off thanks for the extremely helpful guides and taking the time to root this device because the copious amount of OE bloatware is horrible.
2.nd I rooted my 510 and now i have no "home" screen. I can view apps and settings and if i recieve a text i can view it by clicking the notification but if i hit home it goes straight to the google search menu?
I tried a factory reset and nothing.
Thanks in advance.
bdawg the third said:
1.st off thanks for the extremely helpful guides and taking the time to root this device because the copious amount of OE bloatware is horrible.
2.nd I rooted my 510 and now i have no "home" screen. I can view apps and settings and if i recieve a text i can view it by clicking the notification but if i hit home it goes straight to the google search menu?
I tried a factory reset and nothing.
Thanks in advance.
Click to expand...
Click to collapse
Are you running a stock rom or something else? It sounds like Sense isn't installed.
well i was on the stock ROM. but now i think i made the problem worse by trying to fix it. now it wont boot passed the HTC screen. SO i guess i need to try to load a factory boot image?
bdawg the third said:
well i was on the stock ROM. but now i think i made the problem worse by trying to fix it. now it wont boot passed the HTC screen. SO i guess i need to try to load a factory boot image?
Click to expand...
Click to collapse
Yeah, if you've got TWRP installed I would flash a stock rom. CM11 is also usable minus the cameras.
dipspit said:
Yeah, if you've got TWRP installed I would flash a stock rom. CM11 is also usable minus the cameras.
Click to expand...
Click to collapse
Do you have a stock Rom? I cant find one that works. I'm also a huge noob.
bdawg the third said:
Do you have a stock Rom? I cant find one that works. I'm also a huge noob.
Click to expand...
Click to collapse
Who's your service provider?
dipspit said:
Who's your service provider?
Click to expand...
Click to collapse
boost. sorry i thought i posted that
bdawg the third said:
boost. sorry i thought i posted that
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=57042931&postcount=1 V2 Flash that in TWRP.
i get an "unable to open zip" error
bdawg the third said:
i get an "unable to open zip" error
Click to expand...
Click to collapse
What all have you actually flashed or done to the phone? And this error is in TWRP and not fastboot right?
dipspit said:
What all have you actually flashed or done to the phone? And this error is in TWRP and not fastboot right?
Click to expand...
Click to collapse
thats the problem im not %100 sure. im pretty sure i have no OS currently flashed. and yeah the error is in twrp
bdawg the third said:
thats the problem im not %100 sure. im pretty sure i have no OS currently flashed. and yeah the error is in twrp
Click to expand...
Click to collapse
How are you getting the zip over to the phone? Use adb push or an external sd card. You might need to wipe (factory reset) in TWRP before you try and install.
Ok it opened the zip and says flashed successful. now its just sitting on the htc boot screen hmm
bdawg the third said:
Ok it opened the zip and says flashed successful. now its just sitting on the htc boot screen hmm
Click to expand...
Click to collapse
Sounds like a problem with boot. Do a factory reset in TWRP, flash http://forum.xda-developers.com/showpost.php?p=57174863&postcount=1 and then afterwards flash that ROM.
Download the zip in this post and adb push that file to your TWRP/BACKUPS/ folder and restore like that. I forgot the other ROM I had you flash required a previous backup to have been made.
nope still stuck on the htc boot
bdawg the third said:
nope still stuck on the htc boot
Click to expand...
Click to collapse
I edited my post after posting. Did you try that?
dipspit said:
I edited my post after posting. Did you try that?
Click to expand...
Click to collapse
Im getting an unable to find partition for path error?
bdawg the third said:
Im getting an unable to find partition for path error?
Click to expand...
Click to collapse
Regarding http://forum.xda-developers.com/desire-510/development/virgin-sprint-htc-desire-510-stock-t2961521 , are you going about it this way?
There's not really a rom that you can flash without already having a backup. If all else fails you can fastboot oem lock and then run the Sprint 510 RUU from http://www.htcdev.com/devcenter/downloads
dipspit that last link did it! Thank you so much for your help. Ive learned my lesson about not making backups haha.

PLEASE HELP!!!! Nexus 6 with LOCKED boot loader stuck in BOOTLOOP with stock recovery

so here is what happened, i was rooted with an unlocked boot loader running chroma rom. i then tried to unroot my device to return completely back to stock. After the process was done, i formatted and wiped everything then did a reboot. when android started up chroma rom was still on there and i can't access developer settings to unlock my boot loader to flash stock image. so now i am stuck with a locked boot loader and a bootloop device. i have tried adb sideload and got back 2 errors that the footer is wrong and the signature. i don't know what to do now. so Please Help! thank you in advance.
another thing i should add, i only have access to stock recovery
i think this toolkit got a boot loop fix although i have never tried it
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
ChiefEli said:
so here is what happened, i was rooted with an unlocked boot loader running chroma rom. i then tried to unroot my device to return completely back to stock. After the process was done, i formatted and wiped everything then did a reboot. when android started up chroma rom was still on there and i can't access developer settings to unlock my boot loader to flash stock image. so now i am stuck with a locked boot loader and a bootloop device. i have tried adb sideload and got back 2 errors that the footer is wrong and the signature. i don't know what to do now. so Please Help! thank you in advance.
another thing i should add, i only have access to stock recovery
Click to expand...
Click to collapse
do you have twrp recovery, or the stock recovery?
i have stock recovery
linezero said:
i think this toolkit got a boot loop fix although i have never tried it
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
Click to expand...
Click to collapse
ChiefEli said:
i have stock recovery
Click to expand...
Click to collapse
The only option is try and fastboot format userdata and fastboot format cache.
If they don't work, there is no fix. Nothing a toolkit can do.
yup, @danarama has the right explanation. problem is that with stock recovery it most likey will not work. sorry
simms22 said:
yup, @danarama has the right explanation. problem is that with stock recovery it most likey will not work. sorry
Click to expand...
Click to collapse
damn, well i will try it using the toolkit and let you know how it goes.
ChiefEli said:
damn, well i will try it using the toolkit and let you know how it goes.
Click to expand...
Click to collapse
good luck!
at the very least, it might help you fix the bootloop.
ChiefEli said:
damn, well i will try it using the toolkit and let you know how it goes.
Click to expand...
Click to collapse
Has to have unlocked bootloader for that toolkit option to work.
prdog1 said:
Has to have unlocked bootloader for that toolkit option to work.
Click to expand...
Click to collapse
simms22 said:
Click to expand...
Click to collapse
Here is the option. Direct from Wug's FAQ. "If you device is bootlooping or can’t boot up, use “Flash Stock + Unroot” with the “Soft-Bricked/Bootloop” option and follow the onscreen instructions for manually booting your device into bootloader mode and restoring your device."
Can't use flash stock option without an unlocked bootloader.
prdog1 said:
Here is the option. Direct from Wug's FAQ. "If you device is bootlooping or can’t boot up, use “Flash Stock + Unroot” with the “Soft-Bricked/Bootloop” option and follow the onscreen instructions for manually booting your device into bootloader mode and restoring your device."
Can't use flash stock option without an unlocked bootloader.
Click to expand...
Click to collapse
oh well, another "brick"..
simms22 said:
oh well, another "brick"..
Click to expand...
Click to collapse
Pretty much. I have to concur.
prdog1 said:
Pretty much. I have to concur.
Click to expand...
Click to collapse
its sad really. but this happens so often that i dont feel as bad about it anymore. now thats sad
simms22 said:
its sad really. but this happens so often that i dont feel as bad about it anymore. now thats sad
Click to expand...
Click to collapse
Why is this happening so often. Sorry but getting late to the party, I just bought my N6 from Best Buy and have been trying to get caught up on all the reading before it gets here. Is it user error or something else?
BTW, from what I see he can probably break it down and sell the parts on ebay then get close to a new one for $350.
byrdcfmma said:
Why is this happening so often. Sorry but getting late to the party, I just bought my N6 from Best Buy and have been trying to get caught up on all the reading before it gets here. Is it user error or something else?
BTW, from what I see he can probably break it down and sell the parts on ebay then get close to a new one for $350.
Click to expand...
Click to collapse
We don't know but this sucker likes to bootloop. Never relock the device till after it boots and running. Concerning relocking non-stock have seen it bork TWRP and kernel.
byrdcfmma said:
Why is this happening so often. Sorry but getting late to the party, I just bought my N6 from Best Buy and have been trying to get caught up on all the reading before it gets here. Is it user error or something else?
BTW, from what I see he can probably break it down and sell the parts on ebay then get close to a new one for $350.
Click to expand...
Click to collapse
because many people dont read and educate themselves beforehand.
I don't understand why people are re-locking their boot loader. Unless you are returning the device, what is the purpose of re-locking it? I don't get, in this particular thread, why or how the boot loader got locked?
BladeRunner said:
I don't get, in this particular thread, why or how the boot loader got locked?
Click to expand...
Click to collapse
And that is a key question.
I was trying to get ready to turn in my nexus 6 and so I flashed a stock rom (apparently minus the recovery) and relocked my device. I now have twrp but stock 5.1 installed. twrp boots okay but internal storage is 0mb and it appears unable to format partitions. any ideas on a resolution? very comfortable with fastboot (bootloader loads normally) but can't seem to get anything working otherwise.

Draining battery!!

I've recently rooted my device. I installed TWRP, AND everything went well. Kept the root for a couple of days, and then deleted it because I didn't like it. I didn't face any problems while having the root on. However, once I unrooted my device, by installing a new OS on my Note5, I've been having battery issues. I leave the phone on at night, and in the morning, I find that the battery is at least 30% gone! While rooting aND unrooting my device, all the threads were successful. However, I still can't find why my battery is draining so fast. Any suggestions on how to fix this?
If you are unrooted. It's because your device won't go into deepsleep... so you need to reroot.. or install a custom kernel
LiL_Assassin said:
If you are unrooted. It's because your device won't go into deepsleep... so you need to reroot.. or install a custom kernel
Click to expand...
Click to collapse
I'm new to androidand rooting, but I know the fundamentals. I've been trying to get the latest SuperSu, which says that fixes deep sleep automatically, but can't find a reliable source to get it from. Can you please help me out here and get me a link to one? I'd really appreciate it
avk.19xx said:
I'm new to androidand rooting, but I know the fundamentals. I've been trying to get the latest SuperSu, which says that fixes deep sleep automatically, but can't find a reliable source to get it from. Can you please help me out here and get me a link to one? I'd really appreciate it
Click to expand...
Click to collapse
https://download.chainfire.eu/964/SuperSU/BETA-SuperSU-v2.74-2-20160519174328.zip
LiL_Assassin said:
https://download.chainfire.eu/964/SuperSU/BETA-SuperSU-v2.74-2-20160519174328.zip
Click to expand...
Click to collapse
So just to be clear. I'd root my device, same way I did last time, and it'd be fixed? Or should I do another step?
avk.19xx said:
So just to be clear. I'd root my device, same way I did last time, and it'd be fixed? Or should I do another step?
Click to expand...
Click to collapse
Should just need to flash custom recovery and then su and it should be fixed.
LiL_Assassin said:
Should just need to flash custom recovery and then su and it should be fixed.
Click to expand...
Click to collapse
Thank you very much for your help man. I really do appreciate it.
avk.19xx said:
Thank you very much for your help man. I really do appreciate it.
Click to expand...
Click to collapse
No worries man
So there is no way to back to official rom without flash custom kernel? Hmm
I have the same problem with my Note 5, can you please tell me, have you FIX it and how??????

Categories

Resources