Related
Hello All,
Due to my endless frustrations, this might be a long one so please bear with me!
So I purchased a Verizon Global HTC ONE M7 from the States, I am currently in Nigeria and the only thing that makes me sadder and more frustrated than the state of my phone right now is the incessant terror attacks in the country! Initially, almost everything worked fine when i popped in my new Etisalat sim card into the phone, except for the mobile hotspot (which just conveniently turns out to be the one of the top 3 most important features in a phone for me - probably the feature I use the most) this message kept popping up about how hotspot couldn't be used without a VZW sim, etc (also with the non-verizon sim warning when the phone boots up). I tried all I could, eventually deciding to flash a new ROM to clear out everything Verizon and start fresh.
Enter Viperone 6.2.0 - everything worked initially, but after a few weeks i noticed if I did anything like watch a youtube video or download something over a few MBs 90% of the time the data drops (no visible signs like changes from E to H or 3g or the likes, everything looks the same, just that the data stops), toggle mobile data on/off and data connection is back. It worsened and became more frequent over time. Upgraded to Viperone 6.2.1, no difference, so i figured its probably the viperone rom.
Enter Cyanogenmod - http://forum.xda-developers.com/ver...-oneplus-one-stock-rom-cm11s-verizon-t2857425 - and its the same exact issue from the beginning, so im guessing its not to do with the ROM at all (though there are one or two niggling issues with the ROM - cant change BBM display pic, etc)?! I've really tried to comb through the forum and see what makes sense that i could try without bugging y'all - I did a factory reset, wiped everything completely and its the same thing.
I've seen suggestions to similar issues like: flash stock recovery, update radio/firmware/kernel, flash back to custom recovery and some other things which are beginning to sound quite dangerous in my ignorance!! I did believe updating the firmware made sense but after digging deeper, i must honestly say i'm quite confused on what to do. what radio/firmware/kernel works with what software version, etc- most firmware that i've seen are 4.4.3 compatible, while this ROM is 4.4.4., some of them seem to be for stock ROMs only and a lot of other confusions.
So, I'm not gonna be a hero and brick my phone from trying to do what i do not understand, instead here i am, hat in hand, crying out for help after suffering for 3 months! Its really frustrating as, downloads break causing me to lose data, skype or MSLync calls always break and im beginning to look unprofessional to people! This is why I have decided to put up a post of my own specific to my case so i don't medicate for someone else's ailments. So please........ WHAT EXACTLY DO I DO??
PHONE DETAILS (typing it out as i've just realized on this ROM i can't take screenshots with Power+Home button combo anymore and can't be bothered at this point!!!)
ANDROID VERSION: 4.4.4
BASEBAND VERSION: 1.12.41.1112_2
KERNEL VERSION: 3.4.82-gfe09065; [email protected] #1; Wed oct 8 01:36:03 PDT 2014
BUILD DATE: SUN AUG 3 23:00:51 PDT 2014
BUILD NUMBER: CYANOGENMOD 11S v5 (Verizon)
SELinux status: Enforcing
Thanks
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Can you flash stock recovery from Santod's firmware thread and do a factory reset? It could be a corrupt nv partition which would only be fixed by doing a factory reset via stock recovery. (If you must, make a nandroid of system and data in your recovery of choice so you can restore your data if you wish).
Uzephi said:
Can you flash stock recovery from Santod's firmware thread and do a factory reset? It could be a corrupt nv partition which would only be fixed by doing a factory reset via stock recovery. (If you must, make a nandroid of system and data in your recovery of choice so you can restore your data if you wish).
Click to expand...
Click to collapse
Thanks for the responses folks, i'll try out your suggestions and revert..
8100
brymaster5000 said:
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Click to expand...
Click to collapse
So.. i found time to get to this and decided to go with your suggestion of Santod's stock rom... and now, i think i've done the unthinkable!! After WIPING EVERYTHING "All partitions except SD!" as the instructions stated... i attempted to reboot into bootloader and got a message saying "no OS installed, are you sure you want to reboot"... that scared me a bit, but i thought surely, it must be part of the process! I proceed to reboot to bootloader to flash the firmware and i cant seem to do anything!!
Fastboot is stuck on " waiting for device" for everything i try.
Also, i rebooted back into recovery and attempted to install the stock rom: i get the error message "unable to open zip file"..
Have i destroyed my phone with my own hands, people? :crying:
Mr HaRR said:
So.. i found time to get to this and decided to go with your suggestion of Santod's stock rom... and now, i think i've done the unthinkable!! After WIPING EVERYTHING "All partitions except SD!" as the instructions stated... i attempted to reboot into bootloader and got a message saying "no OS installed, are you sure you want to reboot"... that scared me a bit, but i thought surely, it must be part of the process! I proceed to reboot to bootloader to flash the firmware and i cant seem to do anything!!
Fastboot is stuck on " waiting for device" for everything i try.
Also, i rebooted back into recovery and attempted to install the stock rom: i get the error message "unable to open zip file"..
Have i destroyed my phone with my own hands, people? :crying:
Click to expand...
Click to collapse
FALSE ALARM FOLKS!!! I decided to attempt flashing the CM11 rom i just uninstalled and it worked. Turns out its a known issue with the .zip file for that rom - i am now re-downloading from another mirror. Meanwhile the Fastboot thing was just a driver issue - though i'm surprised because i had all the drivers installed on the system and have used fastboot successfully - anyway i reinstalled the drivers and all was well with fastboot again.
NB: Don't get tired of me just yet please!
brymaster5000 said:
Have you tried a stock version of sense? Essentially what our phone was meant to run. Viper uses a lot of custom tweaks for the masses, and sometimes carrier specifics get finicky. I would suggest santods stock Rom, bonestock, or ecliptic. I think nusense uses an international base and not strictly vzw, but you could also try that one...and santod can clarify about the details.
Hope you get it going.
Sent from my One.
Click to expand...
Click to collapse
hello!
Thanks for your ideas guys. I'm currently running Santod's stock rom (which is brilliant, i must say, i actually wanna stay on this rom) since friday - thought i'd give it the whole weekend and see how it goes.. BUT! i still get thoseconnection drops.. and frequently too.
Any other ideas on what the issue could be?
Mr HaRR said:
hello!
Thanks for your ideas guys. I'm currently running Santod's stock rom (which is brilliant, i must say, i actually wanna stay on this rom) since friday - thought i'd give it the whole weekend and see how it goes.. BUT! i still get thoseconnection drops.. and frequently too.
Any other ideas on what the issue could be?
Click to expand...
Click to collapse
If doing factory reset from stock recovery doesn't fix it, it is most likely a burned SIM. It has happened to me. (Average 150+ GB a month in data, so I burn em easily)
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uz has it right, you need to flash a stock recovery and THEN do a factory reset, then reload your custom recovery and rom. I had the exact same issue before. Or you could flash an ruu file which would reset the partitions also.
ccarr313 said:
Uz has it right, you need to flash a stock recovery and THEN do a factory reset, then reload your custom recovery and rom. I had the exact same issue before. Or you could flash an ruu file which would reset the partitions also.
Click to expand...
Click to collapse
Hey folks, apologies for the touch and go nature of this thread - i just don't have a lot of free time on my hands and other reasons..
Anyhow, i think I want to try out ur suggestion of flashing an RUU - I noticed that im unable to actually enter recovery after flashing stock recovery from Santod's thread (i flashed the latest three recoveries). I can get to bootloader, but when i select recovery, the phone goes black for a few seconds and then i get the RED TRIANGLE WITH THE EXCLAMATION MARK INSIDE, obviously something's wrong, few seconds later the phone reboots itself into normal mode. I did do a factory reset from bootloader, but issue persists.
So now to the RUU flashing issue - could you suggest one for me to flash?
By the way though, isn't flashing an ruu gonna take me back to stock completely (as in back to S-ON, ETC..)?
Thanks a whole bunch - IM DETERMINED TO GET THIS TO WORK!!!
Mr HaRR said:
Hey folks, apologies for the touch and go nature of this thread - i just don't have a lot of free time on my hands and other reasons..
Anyhow, i think I want to try out ur suggestion of flashing an RUU - I noticed that im unable to actually enter recovery after flashing stock recovery from Santod's thread (i flashed the latest three recoveries). I can get to bootloader, but when i select recovery, the phone goes black for a few seconds and then i get the RED TRIANGLE WITH THE EXCLAMATION MARK INSIDE, obviously something's wrong, few seconds later the phone reboots itself into normal mode. I did do a factory reset from bootloader, but issue persists.
So now to the RUU flashing issue - could you suggest one for me to flash?
By the way though, isn't flashing an ruu gonna take me back to stock completely (as in back to S-ON, ETC..)?
Thanks a whole bunch - IM DETERMINED TO GET THIS TO WORK!!!
Click to expand...
Click to collapse
That is in fact stock recovery man. When you get the triangle press volume up and power at the same time. You will enter stock recovery.
Any of my ruu will run fine. You won't lose s-off or unlocked status. You flash them in boot loader fastboot mode.
dottat said:
That is in fact stock recovery man. When you get the triangle press volume up and power at the same time. You will enter stock recovery.
Any of my ruu will run fine. You won't lose s-off or unlocked status. You flash them in boot loader fastboot mode.
Click to expand...
Click to collapse
HA! and now i feel :silly: !!
Bless your soul! i'll give it a go shortly...
Hello all.
I've read just about every thread on here about these N7 hard bricks to no avail. My 2013 N7 (Wi-Fi) died one day and I hadn't been using it as much so I didn't notice immediately. I went back to use it to find it hard bricked. I think.
I've used Nexus Root Toolkit to flash multiple different builds of 6.0, 5.0 and 4.3, none of which brought the device back. I've locked and unlocked the bootloader thinking the data wipe might help but it didn't. It is weird, because it simply will not boot up. I have no problem getting into bootloader mode, I have the correct factory images downloaded for flo, nothing works.
After each flash, it just sits on the Google splash screen until I turn it off again.
Any suggestions as to what to do here? I don't know what else to do really.
Thanks,
Sam
droidian1441 said:
Hello all.
I've read just about every thread on here about these N7 hard bricks to no avail. My 2013 N7 (Wi-Fi) died one day and I hadn't been using it as much so I didn't notice immediately. I went back to use it to find it hard bricked. I think.
I've used Nexus Root Toolkit to flash multiple different builds of 6.0, 5.0 and 4.3, none of which brought the device back. I've locked and unlocked the bootloader thinking the data wipe might help but it didn't. It is weird, because it simply will not boot up. I have no problem getting into bootloader mode, I have the correct factory images downloaded for flo, nothing works.
After each flash, it just sits on the Google splash screen until I turn it off again.
Any suggestions as to what to do here? I don't know what else to do really.
Thanks,
Sam
Click to expand...
Click to collapse
Sounds like you prefer only stock roms. Do you insist on it? If you do, my suggestion won't be of help. Otherwise, it looks like your hardware still works. This happened to me once, and what I did was install TWRP recovery and wiped everything, then formatted the storage twice (which, depending on the extent of content, might take up to an hour or more each pass). Seemed the old rom left residues in there that prevented the tab from booting up. Then I flashed a custom rom closest to stock and made sure it booted. If you follow this route up to this point, then you can flash a stock rom anew. Good luck.
graphdarnell said:
Sounds like you prefer only stock roms. Do you insist on it? If you do, my suggestion won't be of help. Otherwise, it looks like your hardware still works. This happened to me once, and what I did was install TWRP recovery and wiped everything, then formatted the storage twice (which, depending on the extent of content, might take up to an hour or more each pass). Seemed the old rom left residues in there that prevented the tab from booting up. Then I flashed a custom rom closest to stock and made sure it booted. If you follow this route up to this point, then you can flash a stock rom anew. Good luck.
Click to expand...
Click to collapse
On this tablet I tend to prefer stock roms however I'm not against custom roms. I will give your suggestion a try. Thanks a lot.
Sent from my VS985 4G using Tapatalk
graphdarnell said:
Sounds like you prefer only stock roms. Do you insist on it? If you do, my suggestion won't be of help. Otherwise, it looks like your hardware still works. This happened to me once, and what I did was install TWRP recovery and wiped everything, then formatted the storage twice (which, depending on the extent of content, might take up to an hour or more each pass). Seemed the old rom left residues in there that prevented the tab from booting up. Then I flashed a custom rom closest to stock and made sure it booted. If you follow this route up to this point, then you can flash a stock rom anew. Good luck.
Click to expand...
Click to collapse
Okay. I flashed TWRP recovery however my touchscreen is not working. So I am now back in the corner.
Do you happen to have any other suggestions?
EDIT: Now the screen is working.
It worked! Thanks a lot. I appreciate it.
Sent from my VS985 4G using Tapatalk
Hi guys.
I have tried to take a logcat of my phone when it bootloops upon restarting after install. Here is the code I used:
Code:
adb -d logcat>C:\adb>Bootloop.txt
However, the output file is empty.
My issue is that I can install any stock-based ROM, but not any custom ROMs (CM or AOSP). When I try to install custom ROMs (CM or AOSP) it always bootloops.
So I am trying to trace the phone when it bootloops. My PC does recognise the phone, as I get the message "This device can perform faster if blah, blah, blah".
Is there another way I can trace the boot up process to find out what errors its throwing out?
Thx in advance.
theKramer
I don't know if USB Debugging is turned on my default on custom ROMs - it isn't on stock ROMs, so logcat wouldn't work via ADB until that would be enabled, which if the custom ROM bootloops from the very start, obviously you wouldn't be able to turn it on.
Have you re-wiped Cache, Dalvik/ART and Data? Flash the appropriate Bootstack? Try moving what you want to keep from your internal storage, eject your MicroSD card/keep it ejected and wipe/reformat your internal storage from TWRP. You can always turn the phone off from TWRP after flashing the custom ROM/Bootstack and then eject the card. Last but not least, try flashing the TOT to start fresh, reroot with the Stump app, put TWRP on with TWRP Manager, and flash the custom ROM and Bootstack like that, although if you go back to stock again after that, I recommend flashing the TOT again before doing so, as some people have trouble with signal or mobile data coming from non-stock or international-stock based ROMs.
Edit: Just noticed you're on the D855, so I don't know the TOT situation there - I only know the VS985, but the advice still stands.
roirraW "edor" ehT said:
I don't know if USB Debugging is turned on my default on custom ROMs - it isn't on stock ROMs, so logcat wouldn't work via ADB until that would be enabled, which if the custom ROM bootloops from the very start, obviously you wouldn't be able to turn it on.
Have you re-wiped Cache, Dalvik/ART and Data? Flash the appropriate Bootstack? Try moving what you want to keep from your internal storage, eject your MicroSD card/keep it ejected and wipe/reformat your internal storage from TWRP. You can always turn the phone off from TWRP after flashing the custom ROM/Bootstack and then eject the card. Last but not least, try flashing the TOT to start fresh, reroot with the Stump app, put TWRP on with TWRP Manager, and flash the custom ROM and Bootstack like that, although if you go back to stock again after that, I recommend flashing the TOT again before doing so, as some people have trouble with signal or mobile data coming from non-stock or international-stock based ROMs.
Edit: Just noticed you're on the D855, so I don't know the TOT situation there - I only know the VS985, but the advice still stands.
Click to expand...
Click to collapse
Hi @roirraW "edor" ehT
This is a long ongoing issue. Basically it surfaced after flashing back to stock as I was having random reboots and thought it might be custom ROM related, but after flashing stock I still had the reboot issues, so figured out battery was toast so changed that and reboot issues were resolved.
But since flashing stock MM on my D855, I cannot get any custom ROM (CM/AOSP) to boot on my ROM except Bumped 5.0.1 ROMs.
I can install any stock or stock-based ROM without any issue, however, custom, no go. The funny thing is that I was running custom ROMs on my phone for more than a year without issue. I could throw any custom ROM at it, and where other people might have issues, my phone would always run them flawlessly.
Not anymore
I have flashed stock Lollipop about 7 or 8 times (via LGUP and LG Flash Tool 2014) and stock KK about another 4 times, so I should have blown out any MM remnants at this stage.
The weird thing is that my phone doesnt boot up with stock based KK either (all of them just hang on bootup), but LP or MM is no issue. I am running LIMITLESS ROM v10.2 at the moment (based on v30a). I cannot remember if I tried v10b actually, I did so many of them..
I have rooted from LP each time, and it is always successful (I have used 3 or 4 different rooting methods) and TWRP is successfully bumped each time.
I have tried numerous versions of TWRP (2.6/2.8/3.0/3.0.2).
I have done a full wipes (cache/dalvik/data/system), even including a format data after and still no luck..
The reason I was asking about methods to get some kind of log info during bootup was so I could maybe get some info on why it doesnt boot custom ROMs..
theKramer said:
Hi @roirraW "edor" ehT
Click to expand...
Click to collapse
Hi! Argh. Sounds really frustrating! Bear with me since it sounds like you know what you're doing and again I have the VS985. Among the 100% stock unrooted you flashed, did you only flash KDZs or is there a TOT available and did you try that? The reason I ask is that TOTs flash more partitions than KDZs and can fix problems that KDZs and ROMs can't. I can personally attest to that but once I experienced it and asked an experienced developer, it became clear that's expected, and when I extracted the partitions out of the VS985 10B TOT and compared to the KDZ I indeed noticed one or two more partitions.
Again, don't mind me if I'm telling what you already know. The other thing is the Bootstack situation, although I haven't ever experienced a bootloop due to the wrong Bootstack, only non-working modem or dangerous combo of our Marshmallow sbl1 partition along with the BUMP-vulnerable 12B aboot (bootloader), necessary for TWRP and for root on Marshmallow. Reference this VS985 post if needed http://forum.xda-developers.com/showpost.php?p=63438031&postcount=2. I don't really expect that to be the issue and since you tried from a variety of stock ROM situations, I wouldn't have expected you to have an issue with every combo you tried.
Edit: actually, the remaining item is the MicroSD card. I know it sounds silly but it's happened. Try it without the card and see what happens. While you're at it, try with the SIM ejected too just for the heck of it, won't hurt to try.
Good luck! Hope you figure it out.
roirraW "edor" ehT said:
Hi! Argh. Sounds really frustrating! Bear with me since it sounds like you know what you're doing and again I have the VS985. Among the 100% stock unrooted you flashed, did you only flash KDZs or is there a TOT available and did you try that? The reason I ask is that TOTs flash more partitions than KDZs and can fix problems that KDZs and ROMs can't. I can personally attest to that but once I experienced it and asked an experienced developer, it became clear that's expected, and when I extracted the partitions out of the VS985 10B TOT and compared to the KDZ I indeed noticed one or two more partitions.
Again, don't mind me if I'm telling what you already know. The other thing is the Bootstack situation, although I haven't ever experienced a bootloop due to the wrong Bootstack, only non-working modem or dangerous combo of our Marshmallow sbl1 partition along with the BUMP-vulnerable 12B aboot (bootloader), necessary for TWRP and for root on Marshmallow. Reference this VS985 post if needed http://forum.xda-developers.com/showpost.php?p=63438031&postcount=2. I don't really expect that to be the issue and since you tried from a variety of stock ROM situations, I wouldn't have expected you to have an issue with every combo you tried.
Edit: actually, the remaining item is the MicroSD card. I know it sounds silly but it's happened. Try it without the card and see what happens. While you're at it, try with the SIM ejected too just for the heck of it, won't hurt to try.
Good luck! Hope you figure it out.
Click to expand...
Click to collapse
Hi.
I didnt know that about there being more partitions in TOT vs KDZ files actually..
I have tried flashing without SD card also already.. I haven't tried without sim card, so why not
Is there a specific reason you mentioned flashing v10b, by the way?
theKramer said:
Hi.
I didnt know that about there being more partitions in TOT vs KDZ files actually..
I have tried flashing without SD card also already.. I haven't tried without sim card, so why not
Is there a specific reason you mentioned flashing v10b, by the way?
Click to expand...
Click to collapse
In the case of the VS985, 10B is the first or earliest build we have, and we have a TOT of it, so I was just using it as an example. I've only ever noticed a leak of one TOT per variant of a device at the most, but if you have more than one available I would choose the earliest.
Mostly useless information to you, but the VS985 does have a 10B KDZ, but it's 10B_01, whereas the TOT is 10B_03. 10B_03 was the official release so it can get OTAs, and 10B_01 was a leak so it can't. From what I've seen, the sub-build _## is only available as part of the filename when you get a hold of the KDZ and TOT. 10B for the VS985 is also the easiest to root because we can just use the Stump app with its brute force option. For us, rooting gets more complicated after 10B and putting TWRP on gets more complicated after 12B. Both 10B and 12B are still KitKat. 23C and 24B 5.0.1 are rootable via PC/USB/adb script. As far as I remember, 35B 5.1.1 and definitely 46A through 48A 6.0 has no method of permanent root, only KingRoot on 35B through 47A which gives temporary and suspicious root.
roirraW "edor" ehT said:
In the case of the VS985, 10B is the first or earliest build we have, and we have a TOT of it, so I was just using it as an example. I've only ever noticed a leak of one TOT per variant of a device at the most, but if you have more than one available I would choose the earliest.
Mostly useless information to you, but the VS985 does have a 10B KDZ, but it's 10B_01, whereas the TOT is 10B_03. 10B_03 was the official release so it can get OTAs, and 10B_01 was a leak so it can't. From what I've seen, the sub-build _## is only available as part of the filename when you get a hold of the KDZ and TOT. 10B for the VS985 is also the easiest to root because we can just use the Stump app with its brute force option. For us, rooting gets more complicated after 10B and putting TWRP on gets more complicated after 12B. Both 10B and 12B are still KitKat. 23C and 24B 5.0.1 are rootable via PC/USB/adb script. As far as I remember, 35B 5.1.1 and definitely 46A through 48A 6.0 has no method of permanent root, only KingRoot on 35B through 47A which gives temporary and suspicious root.
Click to expand...
Click to collapse
So, I haven't actually flashed v10b as I have handed my phone in to a phone repair shop as I have been having a number of hardware issues such as wifi not working, high temperatures at the back of the phone and SIM card detection issues (most likely related to the phone heating up).
However, before I had handed it in to the shop, I flashed a custom kernel (Gabriel stock-based) on the stock ROM I was running at the time, and that reminded me that I have flashed Gabriel kernel on a number of different stock and stock-based ROMs, and if I flashed a stock-based custom kernel, I also got the same bootloop error.
So I was wondering if that might help in any way to pinpoint what is going on with my phone...
theKramer said:
However, before I had handed it in to the shop, I flashed a custom kernel (Gabriel stock-based) on the stock ROM I was running at the time, and that reminded me that I have flashed Gabriel kernel on a number of different stock and stock-based ROMs, and if I flashed a stock-based custom kernel, I also got the same bootloop error.
So I was wondering if that might help in any way to pinpoint what is going on with my phone...
Click to expand...
Click to collapse
I don't think that's specific enough to narrow things down any in this case, but doesn't hurt to note the info! Good luck with your phone!
roirraW "edor" ehT said:
I don't think that's specific enough to narrow things down any in this case, but doesn't hurt to note the info! Good luck with your phone!
Click to expand...
Click to collapse
So my feeling is that there is something up with my boot image, even though my phone is rooted and bumped and TWRP is bumped, there is something my phone doesnt like in AOSP/CM or modified stock-based kernels that is not visible in LG stock.
Is there any tool/script that I can run that would collect info on the boot process...
theKramer said:
So my feeling is that there is something up with my boot image, even though my phone is rooted and bumped and TWRP is bumped, there is something my phone doesnt like in AOSP/CM or modified stock-based kernels that is not visible in LG stock.
Is there any tool/script that I can run that would collect info on the boot process...
Click to expand...
Click to collapse
I'm not very knowledgeable about logs or experienced collecting or looking through them, but maybe collecting a logcat through adb (over USB) while booting would help? You'd have to have USB Debugging turned on, and make sure it stays on across reboots - there's a common issue that is easy to resolve where if USB Debugging doesn't stay on after you reboot, turn it on, plug it into a PC, manually switch the USB connection mode on the phone from MTP and PTP and back to MTP and then disconnect the cable, and it'll stay on then.
roirraW "edor" ehT said:
I'm not very knowledgeable about logs or experienced collecting or looking through them, but maybe collecting a logcat through adb (over USB) while booting would help? You'd have to have USB Debugging turned on, and make sure it stays on across reboots - there's a common issue that is easy to resolve where if USB Debugging doesn't stay on after you reboot, turn it on, plug it into a PC, manually switch the USB connection mode on the phone from MTP and PTP and back to MTP and then disconnect the cable, and it'll stay on then.
Click to expand...
Click to collapse
So, I was suggested the app Liveboot, which was created by Chainfire of SuperSU fame. This app outputs a log to the screen and to a log file on the device of all the calls that are made during bootup (with user selectable level of detail).
Running this app, I did two traces. One with just stock LG and the second after flashing a modified stock kernel..
The stock log is 21KB, the log from when I flashed the modified kernel is 904KB.
Liveboot Stock
Liveboot with kernel
This is not an issue with the modified kernel per se, but with some settings in modified kernels. Any way to pinpoint the offending code/parameter?
This is not directed at you "roirraW "edor" ehT", but to any and all that could help me to figure out what is going on..
theKramer said:
So, I was suggested the app Liveboot, which was created by Chainfire of SuperSU fame. This app outputs a log to the screen and to a log file on the device of all the calls that are made during bootup (with user selectable level of detail).
Click to expand...
Click to collapse
Just wanted to say thanks for a reminder about that app. I had even tested the app when it first came out and I somehow keep forgetting about it.
So I have isolated the issue to some kind of hardware issue.
If I leave my phone turned off for a while with battery out, I can get it to boot custom ROMs. I have tried with 2 different batteries, so its definitely the phone itself. If I reboot the phone once the phone has booted up, then it boot loops again, even if the phone is only booted for a few minutes.
I had to debick my phone a couple of months ago using the short circuit method (due to some stupidity on my part) and it seems that that has fried something in my phone.
Since I brought my phone back to life I have been having issues with Wifi and SD-card slot not working, plus lots of heat and terrible battery life.
I would love to know though what it is in custom ROMs/Kernels that causes my phone to bootloop.
It would be great if I could isolate that somehow.
Anybody have any ideas, by any chance?
I picked up a sprint htc one m9 today. unfortunately no stock OS and no SD CARD with backup either. I booted into twrp but i can not do anything. everything fails. i tried to flash a rom and its a no go. I am stuck and have no idea what to try after looking for hours.
I have no OS
I can boot into twrp
twrp does not allow me to do anything FAILS on every operation.
zwp1990 said:
I picked up a sprint htc one m9 today. unfortunately no stock OS and no SD CARD with backup either. I booted into twrp but i can not do anything. everything fails. i tried to flash a rom and its a no go. I am stuck and have no idea what to try after looking for hours.
I have no OS
I can boot into twrp
twrp does not allow me to do anything FAILS on every operation.
Click to expand...
Click to collapse
Foremost: ugh. Sorry man - that sucks.
So it sounds like your best option would be to get an sd card and apply a RUU from there. Flippy498's Google Sheet is a great resource for where to get them and how to use them.
You might be able to use the Windows-executable RUU directly from Sprint. I'm pretty sure you'd need to be in download mode when you ran it though. It's not as straightforward as the sd card method, but they're usually my first fallback.
Keep in mind that both of these options are destructive - your phone will be brought to a factory state (stock firmware, recovery) and anything on the phone's internal memory will be wiped.
It might be worth exploring why TWRP keeps failing. If we could solve that, you could install the ROM of your choice and not worry about RUUs. But that's definitely more work and probably not necessary if you're not trying to save anything. Once the RUU has been successfully applied, you can just unlock the bootloader anew, install TWRP, and do whatever you want from there.
Thanks a ton that fixed it!
zwp1990 said:
Thanks a ton that fixed it!
Click to expand...
Click to collapse
Wonderful! Enjoy your new phone!
(If you're satisfied with the resolution, the convention in this forum is to mark a thread 'solved' in the title when an issue is resolved. This'll help folks know where to direct their help.)
****** Would really appreciate some help here...
I've tried to install quick reboot (zips), magik, (zips) and busybox, on 3.4 0-0 twrp, and it won't work to boot to system, still says on this version it cannot mount the system. I don't have the perma-recovery file as I cannot find it online, and nexus root toolkit doesn't download it in the dispensaries, latest version.
Hope I haven't knacked it, i also have some screenshots but it doesn't matter as I cannot access the system itself, unless i am missing something it should just boot back to system, I don't understand what I am doing wrong, or have done wrong. Got the img and everything with it.
That said, the mount storage issue is the only thing red, or wrong in the flash, everything else worked apparently, said it installed without a hitch. Which was different that with the standard NRT downloaded twrp, with supersu, as that didn't work.
It just goes back to twrp constantly, can't boot. Help. Really wish I just waited for a response here first. Also I don't believe this is a bootloop, as it just goes back to twrp not bootloader or anything else, probably wrong.
I have been using this vid from the start: realizing that wasn't doing it, magik and a new bionic busybox zip eventually did the trick on 3.4 0-0 twrp, but it sitll won't boot to system. It is probably something obvious, I have been on this for hours today and yesterday, no luck.
only thing i can think of is something to do with: fastboot flash recovery twrp-3.2.1-0-fbe-4core-bullhead.img
basically i flashed the latest version, i dunno if it's supported by nexus 5x.
thanks. uh just please say it ain't bricked.
Anyone?!
edit:
hi all, after immense pain, stress and struggle to get the thing to mount, and trying everything suggested online, it eventually just like "soft-bricked" or whatever, like it was just perma-stuck on the google screen and wouldn't boot to system. i am guessing it's because after a mistake it wiped the system.
i have managed to flash it back to stock, everything is there, and/or redownloading. no way am i gonna bother again, like if it ain't broke don't fix it at this point that would be foolish thought it was perma broke. i'm gonna get a profressional to do it or something, or to give me one to one support to try it again. in the meantime i am going to learn more about rooting and the NRT and all the fundamentals of that.
if anyone here has advice about this still, or articles where I can read about it online, where to learn etc. I'd appreciate that as well, thanks.
Cam3333 said:
****** Would really appreciate some help here...
I've tried to install quick reboot (zips), magik, (zips) and busybox, on 3.4 0-0 twrp, and it won't work to boot to system, still says on this version it cannot mount the system. I don't have the perma-recovery file as I cannot find it online, and nexus root toolkit doesn't download it in the dispensaries, latest version.
Hope I haven't knacked it, i also have some screenshots but it doesn't matter as I cannot access the system itself, unless i am missing something it should just boot back to system, I don't understand what I am doing wrong, or have done wrong. Got the img and everything with it.
That said, the mount storage issue is the only thing red, or wrong in the flash, everything else worked apparently, said it installed without a hitch. Which was different that with the standard NRT downloaded twrp, with supersu, as that didn't work.
It just goes back to twrp constantly, can't boot. Help. Really wish I just waited for a response here first. Also I don't believe this is a bootloop, as it just goes back to twrp not bootloader or anything else, probably wrong.
I have been using this vid from the start: realizing that wasn't doing it, magik and a new bionic busybox zip eventually did the trick on 3.4 0-0 twrp, but it sitll won't boot to system. It is probably something obvious, I have been on this for hours today and yesterday, no luck.
only thing i can think of is something to do with: fastboot flash recovery twrp-3.2.1-0-fbe-4core-bullhead.img
basically i flashed the latest version, i dunno if it's supported by nexus 5x.
thanks. uh just please say it ain't bricked.
Click to expand...
Click to collapse
issues such as what youve experienced are usually caused by version mismatches. I dont have this device and am unfamiliar with the root process for it, but it shouldnt be too different from any other phone. what is the baseband version of your actual phone?
look at this specific reply in this thread
GUIDE - Fix bootloop with locked bootloader via ADB/Fastboot (Android M, N, O)
Hi, Here is fix for those, who have problem with bootloop on 5X with locked bootloader and OEM unlock disabled. This tutorial works for Beta Android O bootloop too. You will need: ADB + drivers installed...
forum.xda-developers.com