Related
Ok, so I ran into a VERY weird issue and was wondering if anyone else has experienced this or has a better solution then what I found.
My Nexus7 was running stock JRO03D. I had it rooted, using the Motley kernel with CWM Recovery - but outside of that, everything else was pretty stock. Anyway, I decided to upgrade to the 4.1.2 image. I pulled the one it downloaded automatically out of /cache and looked at the updater-script to see what it did. I noticed it replaced a lot, including the boot image, so I figured it would be better just to let it do everything and revert my custom stuff later. So I replaced the kernel with the stock JRO03D kernel and, using CWM, flashed the upgrade. Everything seemed to go perfect and it completed the upgrade. Prior to rebooting it, I also flashed the "unofficial" motley 4.1.2 kernel posted on XDA. I rebooted the device, and CWM warned me that 'su' needed to be fixed (how nice!) and made it suid again. It rebooted and after android "updated", everything was up and running. I confirmed in settings that it was on 4.1.2 with the custom kernel. SU was suid root as well. Perfect!
Not quite.
I decided to try rebooting into recovery to make sure CWM was still there, or flash it back if it wasn't. I opened up a terminal emulator, removed the new recovery-recovery image in /system, and did "reboot recovery". The Nexus7 rebooted, but rebooted right back into normal operation. Very weird. So I hooked it up to my computer, figuring CWM was gone, and tried to fastboot flash it back. Fastboot said it did, but I still wasn't able to reboot into recovery. I tried three different versions of CWM and even TWRP, but no dice. Every time I tried rebooting into recovery (using terminal emulator, adb shell or bootloader method) it just went right back into the normal boot process.
I spoke to some people on IRC who recommended reflashing the stock image from Google (without wiping user data). I reflashed the bootloader and then did a fastboot update <stock image>, and it said it replaced boot, recovery, system, etc. It rebooted automatically, and I tried going into stock recovery. That still did NOT work. Instead, I got a very sick looking android guy who was lying down with a red triangle with an exclamation point over him. I was a bit worried and upset at this point. I tried reflashing CWM/TWRP again, but nothing. When I did this, I no longer got the unhappy android image, but it just booted up normally.
I decided to try and doing a more thorough wipe, using fastboot to wipe cache/boot/recovery/system manually. Then I reflashed the bootloader and stock image. Still no recovery (stock or custom).
As you can imagine, I was getting even more concerned now. Especially since I was no without root and no way to get it back (since I couldn't get into recovery to flash the zip for it).
I tried every other thing I could think of to flash recovery back, but nothing worked. It wouldn't load at all.
Finally, I was about to do a complete factory reset and wipe/reflash of everything, but one last thought crossed my mind. I found the older (JRO03D) bootloader and flashed that. Reloaded bootloader and selected "Recovery". Voila, I was in TWRP Recovery Mode! (which was the last one I tried installing). I was able to reinstall my SU.zip and get everything back up and running.
SO, long story short, I'm now on 4.1.2, running the newer unofficial motley kernel and have su back. But I'm also stuck on the older 3.34 bootloader. If I try upgrading it back to 3.41, I won't be able to get into recovery.
Has this happened to anyone else? It doesn't seem like it. Is there a HW issue with my device causing this problem? I can't believe it's software related since I tried two different copies of the 3.41 image. Does anyone have any other suggestions on how I can upgrade the bootloader while keeping the ability to get into recovery mode?
Also, while everything *seems* to be working OK using 3.34, do you think it will cause other problems since I'm using 4.1.2?
Thanks.
*MOD EDIT* please don't quote the entire OP
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
MetalWych said:
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
Click to expand...
Click to collapse
No problem. I'm glad to hear that my solution above helped someone else, and also that I'm not the only one experiencing the problem. I assume you mean you only went back to the JRO03D bootloader and not the whole image, right?
What I'm most concerned about is that it seems like my N7 (and possibly yours as well) is defective. I'm not an uber-expert on Android, but I'm fairly knowledgeable. With a stock system, outside of userdata, that I reflashed multiple times from multiple sources, to have any type of recovery (stock or custom) not work is a bit upsetting. Since it works fine on the older bootloader, it definitely seems to be an issue with that. But since most people do not have the same issue, the only variable I can see being the difference is hardware.
Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It looked more like a warning symbol that something went very wrong then a stock recovery screen.
I've gone into stock recovery on other Android devices before, and it looked similar to CWM. There was a menu that allowed you to install "authorized" update.zip files, factory reset the device, etc. There was no menu here, just a very pissed off and sick looking android guy .
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
There's a big thread around here somewhere with people having the same problem as the op. Unfortunately, staying with the 3.34 bootloader is the only 'fix' I've read about. I still can't figure out why some people run into this problem and some don't. I used twrp to flash the update when it became available, and twrp continued to work afterwards.
spongers said:
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
It took me a long time to find the old full JRO03D update, since Google only has the latest one on their page. I uploaded the bootloader out of it and you can download it here:
http://core.routed.com/bootloader-grouper-3.34.img
Reboot the Nexus7 into bootloader mode and run:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
and then you should be able to flash recovery and get into it.
Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The android with the red triangle does not sound like the stock recovery, it is THE stock recovery.
Under JB 4.1.2 you do not need anymore to connect the N7 to a computer - like it had to be under JB 4.1.1 - to access the bootloader and then the recovery.
Now, pressing volume + power brings the bootloader , the up volume, one press, and then power press put the N7 to recovery. The recovery is the android with the red triangle. To enter in the recovery menu pressing power + volume up brings the menu with the following options:
i) reboot system now,
ii) apply update from ADB,
iii) wipe data/factory reset,
iiii)wipe cache partition.
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
smirkis said:
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
Click to expand...
Click to collapse
Smirkis, my initial thought was that something went wrong in the upgrade process, possibly with the kernel like you suggested, so, as I mentioned in the OP, I flashed everything back to stock 4.1.2. I used flashboot to manually erase boot, cache, recovery and system. I then reinstalled the bootloader from Google's update tarball. I then used fastboot to update to image-nakasi-jzo54k.zip. At this point, outside of wiping sdcard, everything was stock 4.1.2.
While I will admit that I didn't realize that the dead-looking android meant stock recovery (and that's good to hear), subsequently flashing a custom recovery (CWM or TWRP) would continually fail to load it. In fact, I couldn't even boot into the recovery manually without flashing it. While using 100% stock, I attempted to flash three different versions of CWM and one version of TWRP. It claimed it updated, but I was not able to get back into recovery - either through bootloader, adb or "reboot recovery".
I know it's easy for people to always jump to the "user error" answer, but I fail to see how that is the case here. Based on your response, I don't think you actually read what I did and just jumped to the wrong conclusion, especially since I already tried your recommendation and much more. I am not running any custom ROM - everything was always stock outside of recovery, root and kernel. If you can explain your reasoning for thinking I did something wrong in all of my numerous attempts to get it working, I would appreciate it since maybe that would provide a solution. While I did attempt to use a custom kernel originally, that obviously isn't the issue if going back to stock didn't fix it.
Additionally, reverting back to the older bootloader magically fixed everything, while all other attempts failed. Subsequently reinstalling the custom kernel didn't break anything either. So if it wasn't the bootloader and something else was broken, I would assume it would be broken in both versions of the bootloader. The fact that this problem is affecting others, granted a small number, and the same solution works for them, leads me to believe that there is either a bug in the bootloader affecting some N7s or some rare HW defect causing a few of us problems.
There is a conversation about the new android update the boot-loader update and A Power management chip on the nexus 7.. It seems this chip is being changed out. The new chip functions the same as they have been using but Its not compatible with the old boot-loader . The above is the reason for the boot-loader change.. Google is aware of the troubles everyone in this thread is having . I would be looking for a new very tiny update in the near days. Just a guess im wondering if the truth is they are gearing up for the 3g version of nexus .maybe the pm chip being changed has a issue with the added radios. They did say ITS NOT A Chip upgrade but will not say why they are making the switch .
sorry i do not have a link . but everyone knows how to get to google groups ..
Happy Reading..
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
smirkis said:
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
Click to expand...
Click to collapse
Just to clarify, going from bootloader->recovery never worked for me either. Whenever I needed to get into recovery mode, I just opened up a terminal, su'd to root and then ran "reboot recovery", or occasionally doing it via adb. However, those methods always worked for me until I upgraded to the latest bootloader. Then, no custom recoveries would load via any method.
My Nexus7 was first generation. I actually picked it up in Sams Club the day before they were officially released. So if Google made any HW changes in the different revisions, that might explain the difference in results on 4.1.2. Though I imagine most people on XDA also picked theirs up out of the first batch, so I don't think that could be the case. What seems more likely is that there are minor hardware differences that are causing some people's to fail with the 3.41 bootloader, while most don't have that issue. It will be interesting to see if you experience the same issue on your new one though.
gunner1937 said:
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
Click to expand...
Click to collapse
It didn't worked for me. I've tried Rootkeeper apk, but it was useless.
This was driving me crazy until I've found this topic! I've tried resetting it to original settings, using rootkeeper and traditional methods, nothing, zero!
At last, phonic saved my life, and finally I a could root my Nexus 7!
I never responded but my RMA worked as it should. but the issue has been resolved with recovery updates from the developers. the rest of the world who had issues should be good to go. I ended up selling my 16gb unit and got a 32 and it works as it should as well. are we all happy campers now?
Sent from my Nexus 7 using xda premium
I've had similar experiences where the way certain kernels install zips are packaged, the wipe custom recoveries at install. In that situation, I've never wiped anything from system, but rebooted into bootloader and fastboot boot recovery "recovery.img". Then from there install the recovery.zip. The worst is when this happens when you get flash happy away from home and the kernel doesn't work. No way to fix without a comp w/SDK. Glad you're back up and running.
(I cannot be held responsible if the aforementioned damages your device; do the research and own the process.)
I am so glad to have found this thread. This problem was beginning to drive me nuts.
I was in the process of returning the phone back to stock from rooted ICS. Now it won't boot to the system it just keeps booting to CWM. I now have TWRP. Same scenario. Any help would greatly be appreciated.
How would I flash the phone with the AT&T stock ROM? Similar to flashing a bootloader...
mine is also stuck in a boot loop. when i go to exit out of twrp, it says no OS installed. i've used the all in one to try re-installing ICS bootloader and ICS Twrp, then push a rom to the sd card, then flash rom, but still says no OS... what do i do next??(sorry if im thread jacking, but i figured my problem might be similar to yours)
Twiztidunreal said:
mine is also stuck in a boot loop. when i go to exit out of twrp, it says no OS installed. i've used the all in one to try re-installing ICS bootloader and ICS Twrp, then push a rom to the sd card, then flash rom, but still says no OS... what do i do next??(sorry if im thread jacking, but i figured my problem might be similar to yours)
Click to expand...
Click to collapse
Search on these forums for the thrill resurrection guide. That's what I did and it worked. The downside is it took 2 whole evening to accomplish it. Some user learning curve the other is most of the file everything tells you to download have been removed from the servers since the phone is bit outdated.
miketamm said:
Search on these forums for the thrill resurrection guide. That's what I did and it worked. The downside is it took 2 whole evening to accomplish it. Some user learning curve the other is most of the file everything tells you to download have been removed from the servers since the phone is bit outdated.
Click to expand...
Click to collapse
where did you end of finding the files? I noticed they were all down as well, thats why i had not tried that method yet
Twiztidunreal said:
where did you end of finding the files? I noticed they were all down as well, thats why i had not tried that method yet
Click to expand...
Click to collapse
Let me know what you can't find and I'll do my best to back track and see if I can find everything again.
Hi everyone, I 've successfully installed cm11 using Qbking77 tutorial with the CyanogenMod Installer on my htc one but after having some problems with music playback and battery life I've decided to go back to stock.
I've successfully relocked the phone but I can't find the exact Ruu file for my phone and I've tried with other similar ruu but had no luck.
The phone is S On HBBOOT-1.57.000 RADIO -4T.29.3218.08 OS-6.09.401.5
The phone is also stuck in boot loop and recovery mode does not work.
I have found a guy with a similar problem in this site and someone told him to try to run the firmware first and then try to flash TWRP, now the problem is after downloading the firmware file when typing the cmd command adb reboot bootloader it says that it can not find any devices. I'm not really sure what to do now.
Any help appreciated!!!thanks
cesarm96 said:
Hi everyone, I 've successfully installed cm11 using Qbking77 tutorial with the CyanogenMod Installer on my htc one but after having some problems with music playback and battery life I've decided to go back to stock.
I've successfully relocked the phone but I can't find the exact Ruu file for my phone and I've tried with other similar ruu but had no luck.
The phone is S On HBBOOT-1.57.000 RADIO -4T.29.3218.08 OS-6.09.401.5
The phone is also stuck in boot loop and recovery mode does not work.
I have found a guy with a similar problem in this site and someone told him to try to run the firmware first and then try to flash TWRP, now the problem is after downloading the firmware file when typing the cmd command adb reboot bootloader it says that it can not find any devices. I'm not really sure what to do now.
Any help appreciated!!!thanks
Click to expand...
Click to collapse
Firstly, have you enabled usb debugging on your phone? And have you downloaded the most up to date adb drivers and the most up to date HTC drivers?
Because you are s on you cannot flash to downgrade your firmware
Also as your bootloader is now relocked, you cannot flash TWRP either. The bootloader needs to be unlocked to flash custom recovery
There is no RUU available for your phone, so the best option is either a guru reset which will also install stock recovery, or a nandroid backup
stovie_steve said:
Firstly, have you enabled usb debugging on your phone? And have you downloaded the most up to date adb drivers and the most up to date HTC drivers?
Because you are s on you cannot flash to downgrade your firmware
Also as your bootloader is now relocked, you cannot flash TWRP either. The bootloader needs to be unlocked to flash custom recovery
There is no RUU available for your phone, so the best option is either a guru reset which will also install stock recovery, or a nandroid backup
Click to expand...
Click to collapse
about the usb debugging if you are talking before the boot loop happened, yes I had it enable.
I'm gonna try one of those options to see if it works and then I'm gonna report back to let you know what happened.
btw thank you for the reply.
cesarm96 said:
about the usb debugging if you are talking before the boot loop happened, yes I had it enable.
I'm gonna try one of those options to see if it works and then I'm gonna report back to let you know what happened.
btw thank you for the reply.
Click to expand...
Click to collapse
You are welcome, haven't fixed anything yet but come back here again with how things are going
The only way your going to get any function from adb is through recovery, using the sideload method. You should get yourself TWRP and flash using fastboot, then boot to recovery and side load a stockish rom, say viperone or the like. I choose not to run CM or any other AOSP rom for the reasons you listed in OP among others. I currently run ViperOne comming from CM and the battery life is not even comparable. Going back to stock is going to be tough per with your version of hboot s-off is not an easy task as of yet.
MrLizm said:
The only way your going to get any function from adb is through recovery, using the sideload method. You should get yourself TWRP and flash using fastboot, then boot to recovery and side load a stockish rom, say viperone or the like. I choose not to run CM or any other AOSP rom for the reasons you listed in OP among others. I currently run ViperOne comming from CM and the battery life is not even comparable. Going back to stock is going to be tough per with your version of hboot s-off is not an easy task as of yet.
Click to expand...
Click to collapse
I'm quite new to this things so I don't understand much about it, but do you recommend installing a different rom rather then going back to stock? to be honest after all these problems I've had with cm11 I would prefer going back to stock :/
cesarm96 said:
about the usb debugging if you are talking before the boot loop happened, yes I had it enable.
I'm gonna try one of those options to see if it works and then I'm gonna report back to let you know what happened.
btw thank you for the reply.
Click to expand...
Click to collapse
You need to unlock your bootloader first via HTC dev and then flash TWRP recovery
Reboot to recovery and choose to sideload a Rom via adb - download a sense Rom of your choice. There are plenty to chose from
Unfortunately, your going to have a difficult time going back to "Stock." You can use a custom recovery to flash a "Stock" rom, as stovie_steve mentioned, a sense rom. To you the phone will be "Stock" the only difference here is your warranty is void .
108
MrLizm said:
Unfortunately, your going to have a difficult time going back to "Stock." You can use a custom recovery to flash a "Stock" rom, as stovie_steve mentioned, a sense rom. To you the phone will be "Stock" the only difference here is your warranty is void .
Click to expand...
Click to collapse
I unlocked the bootloader and rebooted the phone and everything seems to work fine. But now I don't know what I should do... Now I don't think that I want to go back to stock because it looks a bit difficult and I might end up doing something wrong and brick my phone. Is the viper rom good? I've got cm11 but as I said the battery is draining fast and I still got the music playback problem. Is it hard to install another rom? If it's not I'll probably do it.
cesarm96 said:
I unlocked the bootloader and rebooted the phone and everything seems to work fine. But now I don't know what I should do... Now I don't think that I want to go back to stock because it looks a bit difficult and I might end up doing something wrong and brick my phone. Is the viper rom good? I've got cm11 but as I said the battery is draining fast and I still got the music playback problem. Is it hard to install another rom? If it's not I'll probably do it.
Click to expand...
Click to collapse
Step 1: download a sense based ROM - ARHD, viper one, insertcoin etc onto your phone
Step 2: flash latest TWRP
Step 3: flash the ROM you downloaded
Step 4: **optional** to obtain s off, use firewater or sunshine
Thanks for the help I'm probably gonna try to install the viper one
cesarm96 said:
I unlocked the bootloader and rebooted the phone and everything seems to work fine. But now I don't know what I should do... Now I don't think that I want to go back to stock because it looks a bit difficult and I might end up doing something wrong and brick my phone. Is the viper rom good? I've got cm11 but as I said the battery is draining fast and I still got the music playback problem. Is it hard to install another rom? If it's not I'll probably do it.
Click to expand...
Click to collapse
Personally, ViperOne is the only sense based rom I will use. Its loaded with goodies and stable as they come. But there will be no harm in flashing many roms until you find something you like. Try Viper, do some shopping around, simply do a backup and flash whatever.. dont like it restore your back up. Just remember to have a current back up always. I keep ViperOne and CM installs on the sd as well as backups of both, never know what mood I be in, have the 64GB so I dont mind 5-10GB tied up by these things. Its up to You but Yes I recommend ViperOne,
Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
belowHeights00 said:
Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
Click to expand...
Click to collapse
Reflash whichever recovery you plan to use then remove the battery and put it back in then hold the volume down button and then press and hold the power button at the same time and the phone should then boot to recovery. Make a backup after so you have something to fall back on just in case.
MrMike2182 said:
Reflash whichever recovery you plan to use then remove the battery and put it back in then hold the volume down button and then press and hold the power button at the same time and the phone should then boot to recovery. Make a backup after so you have something to fall back on just in case.
Click to expand...
Click to collapse
Thanks for the reply! I just now gave that a shot but it had no effect.
belowHeights00 said:
Thanks for the reply! I just now gave that a shot but it had no effect.
Click to expand...
Click to collapse
Are you actually holding both buttons down at the same time until the screen turns on? Don't let them go hold them both down until your screen lights up. Then select recovery but if it doesn't work then try below.
Try flashing this version of twrp https://twrp.me/devices/htcdesire510usa32bit.html ... If you're not in the USA I need to know.
Flashing twrp didn't change anything unfortunately. I recently tried re-locking my bootloader and attempted to flash stock images back to the phone but when I press "yes" to the question about voiding the warranty before unlocking the bootloader again...the disclaimer just flashes and the phone won't let it.
Also, I cannot seem to restore it to stock through the menu...nor the bootloader screen.
So now I have "tampered" and "Relocked" banners on top of bootloader screen.
One the upside, the phone itself works fine (I currently only use it for wifi).
Only thing I can think of is I originally flashed a corrupt recovery img (or incompatible version).
Hoping you or someone else has any ideas as to how to get this thing working again. I'd be happy with reverting completly back to stock and starting the process over..
belowHeights00 said:
Flashing twrp didn't change anything unfortunately. I recently tried re-locking my bootloader and attempted to flash stock images back to the phone but when I press "yes" to the question about voiding the warranty before unlocking the bootloader again...the disclaimer just flashes and the phone won't let it.
Also, I cannot seem to restore it to stock through the menu...nor the bootloader screen.
So now I have "tampered" and "Relocked" banners on top of bootloader screen.
One the upside, the phone itself works fine (I currently only use it for wifi).
Only thing I can think of is I originally flashed a corrupt recovery img (or incompatible version).
Hoping you or someone else has any ideas as to how to get this thing working again. I'd be happy with reverting completly back to stock and starting the process over..
Click to expand...
Click to collapse
What service provider are you using?
Don't toss the unlock code you got from HTC you're gonna need the very first one you got keep it forever.
I'm using Boost but I think I figured it out. It ended up being a corrupt download of cmw. I actually used an ruu to get back stock and now the whole process went smoothly. Just looking for a rom that fits...got any recommendations in that area?
belowHeights00 said:
I'm using Boost but I think I figured it out. It ended up being a corrupt download of cmw. I actually used an ruu to get back stock and now the whole process went smoothly. Just looking for a rom that fits...got any recommendations in that area?
Click to expand...
Click to collapse
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
MrMike2182 said:
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
Click to expand...
Click to collapse
Funny enough I never made a backup before and constantly have to re-locate stock images due to soft bricking. I now am making backups so as not to go through that again.
I have a question perhaps you could answer -- if I install a rom that doesn't include any additional tweaks such as extended personaliation options in settings (transitions, etc, etc.)..is there a mod I can flash to achieve that?
belowHeights00 said:
Funny enough I never made a backup before and constantly have to re-locate stock images due to soft bricking. I now am making backups so as not to go through that again.
I have a question perhaps you could answer -- if I install a rom that doesn't include any additional tweaks such as extended personaliation options in settings (transitions, etc, etc.)..is there a mod I can flash to achieve that?
Click to expand...
Click to collapse
For extended personalizing other than developer options, I'd use Xposed.
MrMike2182 said:
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
Click to expand...
Click to collapse
How have you started working on that, i gthink i should join too. Are you working on the USA model or UK? (X86 or X64)
Zubagy said:
How have you started working on that, i gthink i should join too. Are you working on the USA model or UK? (X86 or X64)
Click to expand...
Click to collapse
The USA model because myself and rb don't have the EU phone to even test anything on it.. We still have a lot of booting problems right now. I'd say if you wanted to help I'd have to ask what you know about building roms from source? Have you done it before?
P.S: There's already a CM-12.1 available for the EU model although it does have some issues.. You should read about it if you want to try it..
MrMike2182 said:
The USA model because myself and rb don't have the EU phone to even test anything on it.. We still have a lot of booting problems right now. I'd say if you wanted to help I'd have to ask what you know about building roms from source? Have you done it before?
P.S: There's already a CM-12.1 available for the EU model although it does have some issues.. You should read about it if you want to try it..
Click to expand...
Click to collapse
Not really, But perhaps it time to learn
Zubagy said:
Not really, But perhaps it time to learn
Click to expand...
Click to collapse
It's pretty cool and fun once you get the hang of making things and seeing them function right, and the other thing is... You'll need a pretty decent computer to compile/build with and it'll need to have at least 4GB ram (more is better) and about 50 to 100 GB hard drive space for building your rom plus the CM source code needs to be on your system too...
MrMike2182 said:
It's pretty cool and fun once you get the hang of making things and seeing them function right, and the other thing is... You'll need a pretty decent computer to compile/build with and it'll need to have at least 4GB ram (more is better) and about 50 to 100 GB hard drive space for building your rom plus the CM source code needs to be on your system too...
Click to expand...
Click to collapse
I guess then am good to go, are those the only requirements....... i dont have any source code though
Zubagy said:
I guess then am good to go, are those the only requirements....... i dont have any source code though
Click to expand...
Click to collapse
Well how fast is your internet? By the way.. I'm using a Linux operating system... What are you using? It cannot be done on Windows unless you use a VM.
Hey, I also faced this problem but I find the solution and successfully flash twrp
Hey, I also faced this problem but I find the solution and successfully flash tarp recovery.
belowHeights00 said:
Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
Click to expand...
Click to collapse
MrMike2182 said:
Well how fast is your internet? By the way.. I'm using a Linux operating system... What are you using? It cannot be done on Windows unless you use a VM.
Click to expand...
Click to collapse
Sorry for the delay, yes.... i am using vm ware... my net is not that fast... but it can get things done.
So, I had an issue with the charging port on my Nexus 6 and Motorola is sending out a replacement phone. This is actually the second time this has happened. Anyway, the last time it happened, I was able to get a USB connection and unroot the phone and wipe everything before sending it back to Motorola. This time however, one of the pins on the USB connection has broken and I believe it is one that is used for data transfer and my PC won't recognize the device. I know how to unroot with a computer connection, but I was wondering if anyone knew how to unroot without a computer? I'm still able to move files on and off the phone via wifi, cell and Bluetooth. Thanks in advance for any help.
There's a full unroot option in SuperSU, afterwords you can flash stock rom, not sure how you will get the bootloader locked though
Ok, I found the option in SuperSU for the full unroot. Thanks for that. Now to figure out how to lock the bootloader...
cmorin543 said:
Ok, I found the option in SuperSU for the full unroot. Thanks for that. Now to figure out how to lock the bootloader...
Click to expand...
Click to collapse
Are you already on stock ROM?
I'm currently running PureNexus - the replacement phone is set to arrive tomorrow, so I'm trying to plan ahead since Motorola only allows so many days to receive the old phone before they keep my $500 deposit...
cmorin543 said:
I'm currently running PureNexus - the replacement phone is set to arrive tomorrow, so I'm trying to plan ahead since Motorola only allows so many days to receive the old phone before they keep my $500 deposit...
Click to expand...
Click to collapse
I don't know how you'll be able to flash the stock ROM tbh without fastboot as well as relocking the bootloader. Maybe it would be possible to setup a SSH connection to your phone and send the fastboot commands through there? Not sure, not a pro at this, maybe someone else can lean in here and help you out
Do you have twrp installed, you can copy a stock image over and flash it with twrp. If not, box it up and cross your fingers. I doubt you will have any trouble. Everyone worries about this but never seen anyone say they got denied.
Google The Magnuson Moss Warranty Act. It says manufacturers can't deny warranty unless they can show what you did caused the issue. This is a physical issue, obviously you didn't.
Link to use twrp to flash.
http://www.droidviews.com/now-flash-image-files-using-twrp-2-8-4-0/
Yes, I have TWRP installed. If I can't find another way, I'll flash a stock rom over it and hope for the best. Thanks!!
Couldn't you just take the beta program update and it will take it back to stock?
brando21 said:
Couldn't you just take the beta program update and it will take it back to stock?
Click to expand...
Click to collapse
No because he has twrp installed, it's will fail
Sent from my Nexus 6 using XDA-Developers mobile app
Than maybe I had done something different about a week ago or so. I was on stock rooted with twrp took the update and I'm positive that it flashed stock recovery over twrp. I'm now unrooted with stock recovery. I did not use the computer or manually flashed anything in twrp
brando21 said:
Than maybe I had done something different about a week ago or so. I was on stock rooted with twrp took the update and I'm positive that it flashed stock recovery over twrp. I'm now unrooted with stock recovery. I did not use the computer or manually flashed anything in twrp
Click to expand...
Click to collapse
I can verify that when I first joined the beta program I successfully took the OTA with TWRP and it rebooted to stock recovery.
So what your saying is I should be able to flash a stock rom with twrp and take an ota update and it should go back to the stock bootloader? Will this also relock the bootloader as well?
From what I know it will take everything back to stock except relocking the bootloader. For that you need to fastboot lock the device. What I have read through several sites is that having an unlocked bootloader it will not affect warranty fixes or replacements..