[VIDEO] Oneplus 2 Home Button completely Dead ! - OnePlus 2 Q&A, Help & Troubleshooting

My Home button of the OPT is not giving signs of life. I got the OPT yesterday and it worked but after a clean install it stopped working.
It doesn't do Home Button Taks nor it reads fingerprints. It is simply DEAD! Help me please????
https://www.youtube.com/watch?v=o6ro4YtWwrw
I went through a process of rooting, however I'm still not rooted because no point of rooting if I have this problem.
Here's what happened:
After I unlocked the bootloader and flash TWRP, I went to TWRP and by mistake I wiped system as well. I was so nervous that I ended up wiping: System + Data + Dalvik + Cache + SD Card.
So after I had wiped everything off OPT, of course I had to download and flash manually Oxygen OS ! After I flashed it I set up the phone normally through Setup Wizard and when I was going to configure the Fingerprint, that's when it didn't work anymore. So, everything in the phone is working properly except for the Home Button.
So, do you think it could have anything to do with factory reset + System + SD Card and flashing Oxygen OS again? How could that damage the Home Button ALL functionalities? If not, read the final part of this thread:
The buttons on left and right of the Home Button work properly !
I followed these two Sticky Threads:
---> https://forums.oneplus.net/threads/oneplus-2-stock-rom-collection-updated-01-09.347627/
---> https://forums.oneplus.net/threads/...-custom-recovery-root-efs-backup-more.345478/
I have a theory which might help someone who reads this tell me if it could be it:
So, my OPT came with Oxygen OS 2.0.3 and as I wiped the system, I had to flash a ROM again. However it is only available Oxygen 2.0.2 in the Internet to download, which leads me to think that it was a firmware downgrade which led to this problem. Could this be it?
I am trying to solve this for 17 hours ! Please, if you have any idea how to help me, do not hesitate.
Thanks in advance for all of those who are reading this until the end and even more thanks to the ones replying to this thread !

This could really be due to a driver problem.
They may use different fingerprint readers on several devices.
Have you contacted the Oneplus support yet?

Jann F said:
This could really be due to a driver problem.
They may use different fingerprint readers on several devices.
Have you contacted the Oneplus support yet?
Click to expand...
Click to collapse
I have. But it will take many days, I wish I could fix it asap. So, I guess if it is a driver problem, clean flashing, etc will not do anything ever right?
I have flashed everything from zero serveral times, it just keeps not working

You could search for someone to give you the appropriate files or even a backup of /system
Try the OP forums too.

Jann F said:
You could search for someone to give you the appropriate files or even a backup of /system
Try the OP forums too.
Click to expand...
Click to collapse
I did... The exact same thread as this one lies now on the OP Forums. I guess i'm out of luck.

Same issues as above :| I have a couple backup phones but im still pissed off about this.

We have ruled it down to kernel changes in 2.0.3 vs 2.0.2

i am facing the same problem
my home Button completely gone....
wtf

Backup of /system 2.0.3 posted here

just updated to 2.0.3
same... home bottun STILL not working
basscheck12 said:
Backup of /system 2.0.3 posted here
Click to expand...
Click to collapse

madsatan said:
just updated to 2.0.3
same... home bottun STILL not working
Click to expand...
Click to collapse
If the problem is kernel related, guess you would need a back-up of /boot from 2.0.3 also

basscheck12 said:
If the problem is kernel related, guess you would need a back-up of /boot from 2.0.3 also
Click to expand...
Click to collapse
sorry... so what should i do ?? make a back up and boot it again ??
i updated to 2.0.3 and wipe and boot ...
still not working ....

madsatan said:
sorry... so what should i do ?? make a back up and boot it again ??
i updated to 2.0.3 and wipe and boot ...
still not working ....
Click to expand...
Click to collapse
No... The link I posted was for a back-up of /system but if the issue is kernel related you would also need a back-up of /boot where the kernel is located. Maybe @Jeftha could upload it for you.

basscheck12 said:
No... The link I posted was for a back-up of /system but if the issue is kernel related you would also need a back-up of /boot where the kernel is located. Maybe @Jeftha could upload it for you.
Click to expand...
Click to collapse
by the way
it happened after i flash cyanogen , then I returned to the oxygen 2.02,
but unfortunately it does not work now the home button , not the fingerprint reader , the ability to use it as a button . I lost some drivers or normal?
someone can help me please?

basscheck12 said:
No... The link I posted was for a back-up of /system but if the issue is kernel related you would also need a back-up of /boot where the kernel is located. Maybe @Jeftha could upload it for you.
Click to expand...
Click to collapse
Where can I find this file? When I did the TWRP backup I had boot, system and data partitions selected.

Jeftha said:
Where can I find this file? When I did the TWRP backup I had boot, system and data partitions selected.
Click to expand...
Click to collapse
Oh, I didn't realize you uploaded the entire back-up. Then you have already uploaded the file I was referring to.

having this same issue. home button just stopped working. nandroid back to 2.02 from 2.1 and still doesnt work. if anyone knows a fix please pass along the info

Quizo said:
having this same issue. home button just stopped working. nandroid back to 2.02 from 2.1 and still doesnt work. if anyone knows a fix please pass along the info
Click to expand...
Click to collapse
somehow i deleted all my os and blah blah blah
so i sideload my opt with OxygenOS 2.0 ( OnePlus2Oxygen_14_OTA_002_all_1507251956_wipe.zip)
and i got my home button back ...yay
then flashed the OxygenOS 2.0.2
still have a home button

Facing the same problem. Wasnt flashing one rom over other. Was on hydrogen OS for about 10 days now. Any true solutions to this problem? Does the above solution work?

I've got the same issue starting today. I'm on OxygenOS 2.1.1 with root.
Going back to stock without root to see if it fixes it but I think it's gotta be a hardware issue. Has anyone gone through the RMA process with OnePlus?

Related

[ROOT/RECOVERY] Root and CWM for the Lenovo Yoga 10 HD+ (b8080-h)

I'd appreciate help porting CWM and Cyanogenmod! Please post, fork, request merges etc...
I've managed to compile CWM for the Lenovo Yoga 10 HD+
My repository is here: https://github.com/zyrill/android_device_lenovo_b8080h
And the CWM recovery image is attached. Use towelroot by geohot to root your tablet.
Before attempting to flash, you should:
make sure you know what you're doing!
double check that you're flashing the right partition!
If you flash the wrong partition, you'll brick your tablet!
You can check your partition layout with
Code:
$ ls -al /dev/block/platform/msm_sdcc.1/by-name/
Once rooted, you can flash the image as follows:
Code:
$ adb push recovery.img /storage/sdcard0/recovery.img
$ adb shell
$ dd if=/storage/sdcard0/recovery.img of=/dev/block/mmcblk0p21
Enjoy!
Changelog:
v 0.1: Initial version. Known issue: can't yet mount /sdcard and external cards
v 0.2: Backup is operative! Known issues: no option to backup to external storage, no option to skip backing up of external storage, date is not set correctly
zyrill said:
I'd appreciate help porting CWM and Cyanogenmod! Please post, fork, request merges etc...
I've managed to compile CWM for the Lenovo Yoga 10 HD+
Click to expand...
Click to collapse
Very nice @zyrill!!!! :good:
Thank you so much!
Did anyone tested it yet?
Regards,
Asmaron
asmaron said:
Very nice @zyrill!!!! :good:
Thank you so much!
Did anyone tested it yet?
Regards,
Asmaron
Click to expand...
Click to collapse
Yep! I´ve done! TowelRoot works.
And It works fast and without problems. I have used the tr.apk with date 04.07.2014 and done on the
B8080 with Firmware B8080_S102202_140716_ROW_3GData
Needs 2-3 Seconds and now I have root! But don´t forget to install SuperSu!
Bringer1 said:
Yep! I´ve done!
And It works fast and without problems. I have used the tr.apk with date 04.07.2014 and done on the
B8080 with Firmware B8080_S102202_140716_ROW_3GData
Needs 2-3 Seconds and now I have root!
Click to expand...
Click to collapse
Thanks! I'll give it a try later on!
asmaron said:
Thanks! I'll give it a try later on!
Click to expand...
Click to collapse
Well don't worry, I've got it running on my tablet for all that time now and of course it works, else I wouldn't have posted it. If I find some more time, I'll start porting CM as well, but that might be a while, I'm a bit busy right now.
Most Excellent
zyrill said:
Well don't worry, I've got it running on my tablet for all that time now and of course it works, else I wouldn't have posted it. If I find some more time, I'll start porting CM as well, but that might be a while, I'm a bit busy right now.
Click to expand...
Click to collapse
I installed this and it seems to be working. I backed up my current configuration but have not yet tried to restore anything. The backup did take a while though. I was a little worried at first that it was stuck.
zyrill, you need a donate button somewhere. I'm willing to donate to have cwm running on my tablet. CM 11 would be nice too but I'm just happy to be able to run Exposed and back everything up.
Mark
Oh Yeah
Oh yeah, I forgot to mention that I've got the WiFi only version. That's the 8080-f hardware version. The recovery block is the same.
B5Pilot said:
I installed this and it seems to be working. I backed up my current configuration but have not yet tried to restore anything. The backup did take a while though. I was a little worried at first that it was stuck.
zyrill, you need a donate button somewhere. I'm willing to donate to have cwm running on my tablet. CM 11 would be nice too but I'm just happy to be able to run Exposed and back everything up.
Mark
Click to expand...
Click to collapse
I tried the CWM recovery, and it didn't work for me. (Wifi-only HD+)
flashing worked fine, and I was able to boot into CWM
tried to run a backup, the display stopped changing at (quoting from memory here) "backing up sd-ext" - I have no ext-partition on my sdcard (64GB)...
1st try, switched off after ca. 2 hours: a folder clockworkmod\backup was created on the sdcard, but was empty
2nd try: let it run overnight until the battery ran out. Result: corrupted filesystem on the sdcard, had to re-install from scratch.
Does anybody have the original recovery.img for me to flash it back?
tdklaus said:
I tried the CWM recovery, and it didn't work for me. (Wifi-only HD+)
flashing worked fine, and I was able to boot into CWM
tried to run a backup, the display stopped changing at (quoting from memory here) "backing up sd-ext" - I have no ext-partition on my sdcard (64GB)...
1st try, switched off after ca. 2 hours: a folder clockworkmod\backup was created on the sdcard, but was empty
2nd try: let it run overnight until the battery ran out. Result: corrupted filesystem on the sdcard, had to re-install from scratch.
Does anybody have the original recovery.img for me to flash it back?
Click to expand...
Click to collapse
I may have a little premature in my enthusiasm. My backup included a full copy of my SD card which nearly filled the remaining internal memory. I never did try to restore the backup so I can't guarantee that it would work correctly.
I've started the process of compiling a version of CWM for the WiFi only version but I'm new to the whole process and it will take me a while to begin to figure it out.
Unfortunately I wasn't careful and never extracted the stock recovery before I flashed this version. I was double stupid and never tried to capture the ota to 4.4. I suppose you could do a factory reset and start over. Sucks I know.
Mark
B5Pilot said:
Unfortunately I wasn't careful and never extracted the stock recovery before I flashed this version. I was double stupid and never tried to capture the ota to 4.4. I suppose you could do a factory reset and start over. Sucks I know. Mark
Click to expand...
Click to collapse
I have captured the OTA to 4.4, so if you tell me how, I could try to extract the original recovery from it.
CM 11 would be great
Thanks for your attention to our HD+ tablets. I have B8080-F. Lenovo seems to be pretty slow in bringing new Android versions to this new tablet. It would be great to have CM 11 builds for this device. I have a Samsung Tab 2 7.0 that got new life after I installed CM 11 4.4.4..Just my encouragement to you folks who know how to build CM for the HD+.
Edit:
4.4.2 firmware have WiFi problems,problems with some apps like weather and so on. I went back to 4.3
Can anybody confirm the issues with the backup/restore process? It seemed to work fine for me. Maybe the exact steps to reproduce the mistaken behaviour will help us fix it. Also, I have the original recovery image, is it still needed?
Regarding CWM: I've just finished my PhD and am looking for a job. As soon as that's settled, I'll have time to work on other projects such as CM for our tablet. But in the meantime, if anybody makes any headway, simply issue a pull request and I'll include your work in our repository so everybody can benefit.
Cheers!
zyrill said:
Can anybody confirm the issues with the backup/restore process? It seemed to work fine for me. Maybe the exact steps to reproduce the mistaken behaviour will help us fix it. Also, I have the original recovery image, is it still needed?
Click to expand...
Click to collapse
thx, zyrill.
Well what cam I say, booted into recovery, chose backup/restore - backup and after a few messages the process seemingly stopped with "backing up /sd-ext" on the screen.
No ext-partition existed on the external sdcard, and there were about 10GB free on the internal and 27GB on the external, so wherever CMW tries to store it's files, I hope there was ample room.
I'd still very much appreciate the original recovery.img before I do any more experiments (it's the wife's tablet, after all
zyrill said:
Also, I have the original recovery image, is it still needed?
Click to expand...
Click to collapse
Hi zyrill, I appreciate that you don#t have much time now, but could you still please upload the original recovery?
I managed to get through a backup process in CWM without error messages. Let's trade hostages :laugh:
tdklaus said:
Hi zyrill, I appreciate that you don#t have much time now, but could you still please upload the original recovery?
I managed to get through a backup process in CWM without error messages. Let's trade hostages :laugh:
Click to expand...
Click to collapse
Sure, I'll upload the files once I get back to Germany next Tuesday. Am away and without access to something else than Android... I'll get right on it once I'm back.
Alright, excuse my belated reply. But here we go: I have uploaded the original recovery.img - see the attachment.
I have rooted through towelroot, haven't touched the recovery. I got the "b8080_s101103_140715_row_wifi" update but it failed to apply because of the LenovoSafeCenter.apk being altered.
Any way to update ?
Edit : I tried to restore the factory settings. The update still won't install.
DannyBiker said:
(...)because of the LenovoSafeCenter.apk being altered.
Click to expand...
Click to collapse
I don't think this has anything to do with towelroot as it doesn't alter any of your apk's. But anyway, for your convenience, here's an unaltered version of that file (see att.). Cheers!
Cool thanks ! I'll try that tonight...

[Q&A] [ROM][AOSP][5.0.0_r2 LRX21M][BSZAospLP v1.0][SuperSU|BusyBox][06/11/14]

Q&A for [ROM][AOSP][5.0.0_r2 LRX21M][BSZAospLP v1.0][SuperSU|BusyBox][06/11/14]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][AOSP][5.0.0_r2 LRX21M][BSZAospLP v1.0][SuperSU|BusyBox][06/11/14]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
keith.valdez said:
If I'm flashing from an All F2Fs Ext4 rom, are there any special preparations I need to perform to ensure I don't brick? I would like to flash it but I want to ensure that there are few caveats first. Thanks.
Click to expand...
Click to collapse
Make sure you change the partitions filesystem in TWRP to ext3 or it will not work!
NUMB401 said:
Make sure you change the partitions filesystem in TWRP to ext3 or it will not work!
Click to expand...
Click to collapse
Exactly - if coming from All-F2FS in recovery put cache and data back to ext4 otherwise when you boot it will think your tablet is encrypted and ask for a password!
Thanks for the ROM. However a tilapia(3g) version would be greatly appreciated!
Click to expand...
Click to collapse
I have built Lolipop from source for it but 3G does not seem to be working with radio from KitKat (and I don't know where to get another radio.img)
failing Google+ apk
Trying to install google+ and it keeps failing any ideas? I've tried the past 3 versions and it won't work.
irishman13 said:
Trying to install google+ and it keeps failing any ideas? I've tried the past 3 versions and it won't work.
Click to expand...
Click to collapse
Known incompatible for now. Rest assured it'll be fixed by the ota ?
For those of you still having issues -- make absolutely sure that you've wiped And repaired the cache, data, and system partitions, under TWRP's advanced menu (you have to select each 1 at at time). It takes like 1-2 secs per partition. Without the repair option, you're gonna be stuck on the Google logo forvever.
THEN restart once repaired wiped repaired, and flashed, and don't bother to let TWRP install SuperSU, as the ROM already has it.
---------------
Admin Note: this thread has a dedicated questions and answers section which you can access here -->.
@nickmv is that if you're coming from a f2fs Rom or for everyone?
gsmyth said:
For those of you still having issues -- make absolutely sure that you've wiped And repaired the cache, data, and system partitions, under TWRP's advanced menu (you have to select each 1 at at time). It takes like 1-2 secs per partition. Without the repair option, you're gonna be stuck on the Google logo forvever.
THEN restart once repaired wiped repaired, and flashed, and don't bother to let TWRP install SuperSU, as the ROM already has it.
---------------
Admin Note: this thread has a dedicated questions and answers section which you can access here -->.
@nickmv is that if you're coming from a f2fs Rom or for everyone?
Click to expand...
Click to collapse
Just F2FS
---------- Post added at 12:42 PM ---------- Previous post was at 12:42 PM ----------
irishman13 said:
Trying to install google+ and it keeps failing any ideas? I've tried the past 3 versions and it won't work.
Click to expand...
Click to collapse
Latest GApps newly linked in OP has a working Google+
There is broken "Ok Google" hotword as well as voice search. It just won't listen to me
First off let me say this is awesome and really breathed new life into my old N7! Secondly I used the Tap & Go setup method from an GPE One M8 and it didn't really work all the way but whatever.
The issue is there is now an undismissable notification on my M8 saying setup completed. Any ideas how to get rid of this?
Oh and also has Face Unlock ever been present on the Nexus? Wanted to try it out but wasn't listed as an option. Thanks a ton!
TitBkp
Hi
I have supersu installed but titanium backup doesn't recognise the device is rooted! Any ideas? Other root apps work on android 5 but this one doesn't.
I cannot log into play store since upgrading to lollipop. How can I fix this?
Sent from my AOSP on Grouper using XDA Free mobile app
Successfully installed via multirom, however play store crashes when opened.
am2012 said:
Hi
I have supersu installed but titanium backup doesn't recognise the device is rooted! Any ideas? Other root apps work on android 5 but this one doesn't.
Click to expand...
Click to collapse
Try this beta one:
http://forum.xda-developers.com/showpost.php?p=56629869&postcount=196
When installing the GApps package I get this error: E:Error executing updater binary in zip '/data/media/0/sideload.zip'
I originally got a different one but I remembered I was on the "buggy" 2.7.1.1 version so I updated to latest 2.8.1.1 version and well...this. I've wiped my data/cache/system/all of it and repaired the data n cache and then did this all and still a no go. What am I doing wrong? Am I missing something? The only issue I noticed listed for this was the recovery I used.
S1L3nTShaDoWz said:
When installing the GApps package I get this error: E:Error executing updater binary in zip '/data/media/0/sideload.zip'
I originally got a different one but I remembered I was on the "buggy" 2.7.1.1 version so I updated to latest 2.8.1.1 version and well...this. I've wiped my data/cache/system/all of it and repaired the data n cache and then did this all and still a no go. What am I doing wrong? Am I missing something? The only issue I noticed listed for this was the recovery I used.
Click to expand...
Click to collapse
So issue is just with the GApps zip file? Try flashing the ROM then rebooting recovery I had read in my main thread... Also be sure MD5 matches.
bshiznit said:
So issue is just with the GApps zip file? Try flashing the ROM then rebooting recovery I had read in my main thread... Also be sure MD5 matches.
Click to expand...
Click to collapse
Yes originally it was but I managed to fix it by re-doing it all over again w system repair too, though I believe it was doing it over again that fixed it the system repair could've helped. Anyways new issues now, TWRP claims I have no OS....yet here I am....booted in 5.0 w GApps. Oh well nothing to be upset by I guess, least I fixed it.
S1L3nTShaDoWz said:
Yes originally it was but I managed to fix it by re-doing it all over again w system repair too, though I believe it was doing it over again that fixed it the system repair could've helped. Anyways new issues now, TWRP claims I have no OS....yet here I am....booted in 5.0 w GApps. Oh well nothing to be upset by I guess, least I fixed it.
Click to expand...
Click to collapse
Glad to hear it! Sometimes /system remains mounted so TWRP will incorrectly report missing OS
I guess the mic doesn't work, Shazam doesn't work?
Works great so far! Only issue appears to be the volume buttons (when used for notification volume) results in crashing.

HELP!! I am stuck inside of TWRP and cannot boot into the system

Hey everyone, I have a really frustrating problem, I am currently able to boot into TWRP via hardware method and ADB can see my device as well. However I have tried to install a stock system image through TWRP and I have also tried to install another TWRP backup that a user had posted in the Q&A forum. At one time I was able to successfully boot into the system but my device said encryption unsuccessful. After wiping the system partition and trying to install these images through TWRP I am still unable to boot into the system. Whenever I install them my phone will reboot into TWRP. I am at a loss as to what to do. If anyone has any ideas or suggestions I would appreciate it.
crazyc78 said:
Hey everyone, I have a really frustrating problem, I am currently able to boot into TWRP via hardware method and ADB can see my device as well. However I have tried to install a stock system image through TWRP and I have also tried to install another TWRP backup that a user had posted in the Q&A forum. At one time I was able to successfully boot into the system but my device said encryption unsuccessful. After wiping the system partition and trying to install these images through TWRP I am still unable to boot into the system. Whenever I install them my phone will reboot into TWRP. I am at a loss as to what to do. If anyone has any ideas or suggestions I would appreciate it.
Click to expand...
Click to collapse
I saw your other post in the other thread, but couldn't reply for some reason.. did you wipe the internal storage before restore?
Yes I did wipe the internal storage, I actually wiped everything the first time I tried to get everything in order and that was my original problem by wiping the system. I didn't realize that wiping internal storage would cause issues but that could have been one of the culprits. I think what finally solved my issue is I installed a deodexed rom and then powered down my device instead of rebooting and it booted up the rom. I had to flash SuperSU from a zip because for some reason the one that was preinstalled with that rom didn't install properly. So I installed the SuperSU zip and I am now officially rooted. Lesson learned DON'T WIPE SYSTEM OR INTERNAL STORAGE lol. I should have known better I have been rooting for awhile now, I just wasn't paying attention it happens to the best of us sometimes. Thanks for your help.
crazyc78 said:
Yes I did wipe the internal storage, I actually wiped everything the first time I tried to get everything in order and that was my original problem by wiping the system. I didn't realize that wiping internal storage would cause issues but that could have been one of the culprits. I think what finally solved my issue is I installed a deodexed rom and then powered down my device instead of rebooting and it booted up the rom. I had to flash SuperSU from a zip because for some reason the one that was preinstalled with that rom didn't install properly. So I installed the SuperSU zip and I am now officially rooted. Lesson learned DON'T WIPE SYSTEM OR INTERNAL STORAGE lol. I should have known better I have been rooting for awhile now, I just wasn't paying attention it happens to the best of us sometimes. Thanks for your help.
Click to expand...
Click to collapse
I've been rooting for a while myself but messed up I'm stuck in twrp and don't know how to get it the phone back on! your help would be glady appreciated .
ricosuave88 said:
I've been rooting for a while myself but messed up I'm stuck in twrp and don't know how to get it the phone back on! your help would be glady appreciated .
Click to expand...
Click to collapse
I used the deodexed ROM that is in the development forum. If I can upload it here I will if not just download it put it on your SD card and flash it. It may take a couple tries though I would suggest powering down your phone instead of rebooting it. Then turn it on and it should boot into the new rom. It's basically the same stock rom that our phone comes with. You may have to flash Chainfires SUPERSU zip that's in one of the threads. These steps should get you up and running again. Also if you can see your internal storage you're not encrypted. Hopefully that works for you. Let me know how it goes.
I wasnt able to upload the file from my phone. Just download it from here.
http://forum.xda-developers.com/v20/development/h918-stock-deodex-debloat-t3499423/page5
crazyc78 said:
I wasnt able to upload the file from my phone. Just download it from here.
http://forum.xda-developers.com/v20/development/h918-stock-deodex-debloat-t3499423/page5
Click to expand...
Click to collapse
Thanks for responding back. Man I'm still stuck in twrp I'm losing all hope at this point been at all day and can't figure out what Im doing wrong . I know you was stuck in the same situation did flashing that twrp back up help you out?
ricosuave88 said:
Thanks for responding back. Man I'm still stuck in twrp I'm losing all hope at this point been at all day and can't figure out what Im doing wrong . I know you was stuck in the same situation did flashing that twrp back up help you out?
Click to expand...
Click to collapse
Flashing the rom helped me out. It's a system image file. It's basically the stock rom for our device just deodexed. What exactly happened what did you wipe after your phone booted into
TWRP? If you still have TWRP you're not bricked. If you can flash that image from the thread I copied above then you should be good. You may have to flash SUPERSU to get root back. Also after you flash make sure you're not encrypted if you can see your internal storage partition then you're not encrypted.
crazyc78 said:
Flashing the rom helped me out. It's a system image file. It's basically the stock rom for our device just deodexed. What exactly happened what did you wipe after your phone booted into
TWRP? If you still have TWRP you're not bricked. If you can flash that image from the thread I copied above then you should be good. You may have to flash SUPERSU to get root back. Also after you flash make sure you're not encrypted if you can see your internal storage partition then you're not encrypted.
Click to expand...
Click to collapse
when I flashed the rom from your link above it just booted me into twrp again . I don't know what exactly I'm suppose to wipe. I can see internal storage tho so I guess that's a good sign but what's not good is that I can't use my phone :/ I've been rooting for years and can't seem to figure this one out.
ricosuave88 said:
when I flashed the rom from your link above it just booted me into twrp again . I don't know what exactly I'm suppose to wipe. I can see internal storage tho so I guess that's a good sign but what's not good is that I can't use my phone :/ I've been rooting for years and can't seem to figure this one out.
Click to expand...
Click to collapse
When you flashed the rom did you power the phone down and then try to boot into the rom? That's what I did and it worked for me. So don't select reboot into system, I'm not sure why it doesn't work that way. I had to power my device down and then boot into the room. Also if you can see your internal partition in TWRP then you should be good and encryption is not enabled. I know how frustrating this is. Just keep trying eventually that rom should stick.
crazyc78 said:
When you flashed the rom did you power the phone down and then try to boot into the rom? That's what I did and it worked for me. So don't select reboot into system, I'm not sure why it doesn't work that way. I had to power my device down and then boot into the room. Also if you can see your internal partition in TWRP then you should be good and encryption is not enabled. I know how frustrating this is. Just keep trying eventually that rom should stick.
Click to expand...
Click to collapse
Man, I have tried everything as well and I can't seem to get pass TWRP. Has anyone found a way around this problem? I have been looking around for an answer for 2 days and nothing has worked so far, any help will be greatly appriciated.
Thank you
kaiser10 said:
Man, I have tried everything as well and I can't seem to get pass TWRP. Has anyone found a way around this problem? I have been looking around for an answer for 2 days and nothing has worked so far, any help will be greatly appriciated.
Thank you
Click to expand...
Click to collapse
There a stock rom that I posted a link to a few posts back when I trying to help someone else. Download it put it on your SD card and install it. You don't need to wipe anything it will format things for you. After it installs don't reboot, power down the device and then turn it back on it should boot into the rom. That's what worked for me. I believe there was another way then what I just described it's in the same thread that I linked a few posts back. Good luck!!
crazyc78 said:
There a stock rom that I posted a link to a few posts back when I trying to help someone else. Download it put it on your SD card and install it. You don't need to wipe anything it will format things for you. After it installs don't reboot, power down the device and then turn it back on it should boot into the rom. That's what worked for me. I believe there was another way then what I just described it's in the same thread that I linked a few posts back. Good luck!!
Click to expand...
Click to collapse
Thanks for the help brother. However, it did not work for me. I flash the stock system, boot, turn device off and turn back on but I am still stock on TWRP. I will continue reading and hopefully I will find the answer soon.
thank you,:crying:
kaiser10 said:
Thanks for the help brother. However, it did not work for me. I flash the stock system, boot, turn device off and turn back on but I am still stock on TWRP. I will continue reading and hopefully I will find the answer soon.
thank you,:crying:
Click to expand...
Click to collapse
Np don't give up, I almost lost hope and then it worked for me.
Like I said there was another method that was discussed that worked for someone else. Try this thread, I know someone had the same issue that you and I had and they finally got it working.
http://forum.xda-developers.com/v20/development/h918-stock-deodex-debloat-t3499423
I'm here to the rescue! Follow this to the T! It worked for me! Let me know. http://forum.xda-developers.com/showthread.php?p=69685809
Sent by using the battery of my LG V20
im on the same boat as you. I am stuck in TWRP
tried all the methods i found so far and still stuck in twrp. i would greatly appreciate if someone can get me out of this bootloop!
hslayer said:
tried all the methods i found so far and still stuck in twrp. i would greatly appreciate if someone can get me out of this bootloop!
Click to expand...
Click to collapse
Same. Though I am on US996. Not sure what I did, was exploring some behind the scenes stuff using 'hidden codes' but didn't change any values as I didn't know what they meant in most cases. I rebooted my phone and it went straight to TWRP (3.0.2-1) and it will not boot past TWRP. Occasionally after I've flashed something, it will boot into TWRP and the screen will be unresponsive to touch so I have to pull the battery, but then it will be fine again.
I was in your position not to long ago, I'm currently working on getting a .kdz recovery file for the H918. My progress will continue on it later when finals are over.
netgar post 134
Restore H918 to 100% Stock (!!REQUIRES TWRP!!)

Data encryption issue after cm13

Hi folks, first off English is not my main modus operandi so bear with me thx.
I tried out every room there is for the VNS-L31, CM13 from here, Revolution RC3 from a Spanish forum, Beanstalk and a few others what where more glorified reskins ... anyway before installing CM13 I made a full dump on TWRP but wile forgetting I wasn't on stock but on Revolution RC3, so I ended up with the wrong encryption key for the DATA folder, pardon me internal memory SD ... RRC3 is based on the European Stock B150 with a lot of tweaks, also a not perfect encryption of the internal SD similarly to CM13 problem with the SD.
Here is the main beef I am having, after getting of CM I tried to restore my dump and ended up ****ing up the encryption of the internal memory card. Now I can't got back to say the 161 internalional version and I am kinda bound to the European L31900B versions of the stock rom if I install anything else the accounts like Google or Facebook are not working and anything not installed already on the phone is FC.
I can't format data because of the encryption. Not under fastboot or any of the trwps, tried 3 different ones, I checkted the phone is not frp. I did lock frp and bootloader again and unlocked them so to double make sure I was right on that one. I tried going back to stock with the dload method but no dice data still locked. Delete accounts with root explorer and went back to vnsl31900b130 what seams to be the firmware that I am stuck on now with the ****ed up encryption ....
I am used to flashing stuff left and right but this is new land for me any help would be greatly appreciate ... And my warning DONT SCREW WITH TGE ENCRYPTION ON YOUR PHONE ... ITS A *****!!!!
Cant you just delete the system in TWRP?
Thijs van Hal said:
Cant you just delete the system in TWRP?
Click to expand...
Click to collapse
Nope I deleted everything in TWRP, System, Cust, that is not a problem, the data partition on the other hand I can't format not I twrp, or by fastboot erase/format/-w commands ... Really annoying, never had an issue like this ... Funny that I can delete things with an root explorer under Android and that saving data works fine but the moment I leave the os it just closes up. Even the dump I made can't replace the data partition outside of the os
markus2811 said:
Nope I deleted everything in TWRP, System, Cust, that is not a problem, the data partition on the other hand I can't format not I twrp, or by fastboot erase/format/-w commands ... Really annoying, never had an issue like this ... Funny that I can delete things with an root explorer under Android and that saving data works fine but the moment I leave the os it just closes up. Even the dump I made can't replace the data partition outside of the os
Click to expand...
Click to collapse
Ive never seen that before to, weird man...
I have the same issue. Any fix?
Nemeroz said:
I have the same issue. Any fix?
Click to expand...
Click to collapse
No, but I am starting from scratch, also I am trying to manually corrupt the data partition so to be able to format it ... Just a pain, at the moment I am stuck, maybe if I can get someone else's firmware dump for my phone might do the trick its big so I am not sure anyone would upload something that big ... We see
markus2811 said:
No, but I am starting from scratch, also I am trying to manually corrupt the data partition so to be able to format it ... Just a pain, at the moment I am stuck, maybe if I can get someone else's firmware dump for my phone might do the trick its big so I am not sure anyone would upload something that big ... We see
Click to expand...
Click to collapse
Did you try to Flash stock recovery and do a factory reset?
Or via fastboot do this command :
fastboot format userdata
Sent from my HUAWEI VNS-L31 using XDA Labs
simo255 said:
Did you try to Flash stock recovery and do a factory reset?
Or via fastboot do this command :
fastboot format userdata
Sent from my HUAWEI VNS-L31 using XDA Labs
Click to expand...
Click to collapse
I tried all of them. Nothing worked :crying:
Nemeroz said:
I tried all of them. Nothing worked :crying:
Click to expand...
Click to collapse
So I fixed my problems with BadWolfs help he got me back to stock by flashing a special zip that allowed me to install the firmware from dload on the external sdcard
Thx again for your help
markus2811 said:
So I fixed my problems with BadWolfs help he got me back to stock by flashing a special zip that allowed me to install the firmware from dload on the external sdcard
Thx again for your help
Click to expand...
Click to collapse
Forgot here us the link http://www.htcmania.com/showthread.php?t=1261335
Everything you need to go back to stock from cm13 (if you screw up like me) or nougat beta is in here. Is in spanish but google translate is doing a pretty good job all bloody credit is going to badwolf and his friends
Thx and good night
markus2811 said:
Forgot here us the link http://www.htcmania.com/showthread.php?t=1261335
Everything you need to go back to stock from cm13 (if you screw up like me) or nougat beta is in here. Is in spanish but google translate is doing a pretty good job all bloody credit is going to badwolf and his friends
Thx and good night
Click to expand...
Click to collapse
when you flash the oem info didnt it say unable to mount data? like before?

Soft Reboots Leading to Bootloop

Hey guys, not exactly sure where to post this since this has happened to me both with AICP and now once with Dark Rom. So simply put I am just using my phone and then randomly it soft reboots. I hurry and take some logs before the next. Then the next. Then it keeps doing this with each time between getting shorter until it just won't fully boot up without wiping dalvik and cache.
I am using Dark Rom at the moment with A2017U version and the stock kernel that comes with Darkrom. However I believe I did have it with LlamaSweet as well. The only modifications I have done are magisk and trying out jococ v2 tweak which I doubt either is the cause.
Has anyone had ant issues like this or does anyone know how to fix it? I hate knowing it's random and it may make my alarm clock not go off if it is in a bootloop.
Hope to get some help with this! Thanks!
JTruj1ll0923 said:
Hope to get some help with this! Thanks!
Click to expand...
Click to collapse
Just realized the zip posted has only files that are blank.... So here is a log I grabbed from TWRP. Hopefully this will help instead!
JTruj1ll0923 said:
Just realized the zip posted has only files that are blank.... So here is a log I grabbed from TWRP. Hopefully this will help instead!
Click to expand...
Click to collapse
No idea, not a dev. But I've read somewhere that Magisk 14.5 might be the culprit. I had this exact same problem on LineageOS. I made a backup of the system that was doing this, then wiped system and data, flashed LOS, booted it, then went to TWRP, wiped system and data, and restored the backup (only system, boot and data backed up). That solved it until you rebooted or the phone just decided to reboot itself...
Choose an username... said:
No idea, not a dev. But I've read somewhere that Magisk 14.5 might be the culprit. I had this exact same problem on LineageOS. I made a backup of the system that was doing this, then wiped system and data, flashed LOS, booted it, then went to TWRP, wiped system and data, and restored the backup (only system, boot and data backed up). That solved it until you rebooted or the phone just decided to reboot itself...
Click to expand...
Click to collapse
By doing this what would be the benefit? From what I can see you are basically back at point A by restoring the files. But yeah I do have magisk 14.5 installed... I had some problems with 14 but I'll see if I can get it to work this time. Thanks!
JTruj1ll0923 said:
By doing this what would be the benefit? From what I can see you are basically back at point A by restoring the files. But yeah I do have magisk 14.5 installed... I had some problems with 14 but I'll see if I can get it to work this time. Thanks!
Click to expand...
Click to collapse
Yes, it seems like it would do nothing, but it actually fixed my phone every time.
Maybe you can try the magisk uninstaller zip, dunno
Choose an username... said:
Yes, it seems like it would do nothing, but it actually fixed my phone every time.
Maybe you can try the magisk uninstaller zip, dunno
Click to expand...
Click to collapse
Thats Interesting. Well it happened again and logs were empty again... So I moved back to magisk 14.0 if that doesn't work I'll try restoring system and data.
@JTruj1ll0923,,
Hi,
you can try to backup before hard reset your phone. Usually, the LlamaSweet and DARK ROM are not compatibile with A2017G, so ZTE stock ROM would be a better choice.
William Guo said:
@JTruj1ll0923,,
Hi,
you can try to backup before hard reset your phone. Usually, the LlamaSweet and DARK ROM are not compatibile with A2017G, so ZTE stock ROM would be a better choice.
Click to expand...
Click to collapse
Thanks but I have a a2017u. Don't know if that makes much a difference though.

Categories

Resources