I tried to flash a kernel and now the phone will not stop bootlooping. Can't get into fastboot or anything. Any suggestions?
I held all sorts of keys down and now it's in fastboot mode so I think I'm good. This I can recover from.
bobby janow said:
I tried to flash a kernel and now the phone will not stop bootlooping. Can't get into fastboot or anything. Any suggestions?
I held all sorts of keys down and now it's in fastboot mode so I think I'm good. This I can recover from.
Click to expand...
Click to collapse
If you are in the fastbootd. Try this;
fastbboot reboot bootloader
Once your are there, you can flash the stock boot image to get you going again.
vandyman said:
If you are in the fastbootd. Try this;
fastbboot reboot bootloader
Once your are there, you can flash the stock boot image to get you going again.
Click to expand...
Click to collapse
Thanks, yeah I just reflashed the Proton rom once I got into fastboot. The problem was it went to the page with the orange type saying you device is unlocked and unsecure blah, blah. Hit power button to pause and once again to resume. Then it went right back to that. So there was no fastboot available it just kept cycling through. I then held the power button and every other button I could find and it finally went to fastbootd. Once there I breathed a sigh of relief I knew I could recover from that. I used the auto installer from Proton and now I'm back but probably on the December radio. I'm not messing around any more today, enough stress. Time to look at some animals. ;-) Great pic btw. Post that if you can, you know where. Thanks for the advice and quick response.
bobby janow said:
Thanks, yeah I just reflashed the Proton rom once I got into fastboot. The problem was it went to the page with the orange type saying you device is unlocked and unsecure blah, blah. Hit power button to pause and once again to resume. Then it went right back to that. So there was no fastboot available it just kept cycling through. I then held the power button and every other button I could find and it finally went to fastbootd. Once there I breathed a sigh of relief I knew I could recover from that. I used the auto installer from Proton and now I'm back but probably on the December radio. I'm not messing around any more today, enough stress. Time to look at some animals. ;-) Great pic btw. Post that if you can, you know where. Thanks for the advice and quick response.
Click to expand...
Click to collapse
What exactly where you trying to accomplish?
Remember that if you ever run into trouble, you can reflash to stock using the Android Flash Tool.
To reboot into bootloader, hold Power + Volume Down. If the device is bootlooping, just hold Volume Down.
Then, connect the USB cable, go to Android Flash Tool, select the build you want to install, and be sure to uncheck the Wipe Device and Lock Bootloader options.
Most of the time this won't be necessary though - you can just reflash the factory boot image. Here is my guide on rooting which hopefully will provide a bit more insight and information into the process. You'd simply reflash the boot.img from the factory image zip.
Also, if you're interested in updating, my guide can help you do that too.
V0latyle said:
What exactly where you trying to accomplish?
Remember that if you ever run into trouble, you can reflash to stock using the Android Flash Tool.
To reboot into bootloader, hold Power + Volume Down. If the device is bootlooping, just hold Volume Down.
Then, connect the USB cable, go to Android Flash Tool, select the build you want to install, and be sure to uncheck the Wipe Device and Lock Bootloader options.
Most of the time this won't be necessary though - you can just reflash the factory boot image. Here is my guide on rooting which hopefully will provide a bit more insight and information into the process. You'd simply reflash the boot.img from the factory image zip.
Also, if you're interested in updating, my guide can help you do that too.
Click to expand...
Click to collapse
Thanks, yeah Android Flash tool was my fallback but only if I could get into fastboot. Once I got there recovery is just a matter of what I wanted to do. Ahh.. so it was the volume down key that got me out. I held the power button to no avail, power and up didn't work, then I hit the down button out of sheer frustration and boom, I was able to breathe again. Great learning experience though. If I didn't have XDA I would probably have passed out but I knew you guys would come through.
I'm just not into rooting lately but it might be coming soon again. I'm extremely frustrated with Google these days. I would love to flash a kernel such as CleanSlate or BluSpark but everyone running my scenario seems to be rooted. Proton is running pretty good but the stock kernel leaves something to be desired. I'll keep at it though. Thanks again.
BBJAN - Iended up in the same situation exactly as you did about 2 weeks ago. ProtonAOSP web installer may work for some, but not me. I installed manually as per the website instructions and it installed 1st time. If the web installer doesn't work go straight to the manual install.
bobby janow said:
Thanks, yeah Android Flash tool was my fallback but only if I could get into fastboot. Once I got there recovery is just a matter of what I wanted to do. Ahh.. so it was the volume down key that got me out. I held the power button to no avail, power and up didn't work, then I hit the down button out of sheer frustration and boom, I was able to breathe again. Great learning experience though. If I didn't have XDA I would probably have passed out but I knew you guys would come through.
I'm just not into rooting lately but it might be coming soon again. I'm extremely frustrated with Google these days. I would love to flash a kernel such as CleanSlate or BluSpark but everyone running my scenario seems to be rooted. Proton is running pretty good but the stock kernel leaves something to be desired. I'll keep at it though. Thanks again.
Click to expand...
Click to collapse
Did you get into issue rooting Proton? what exactly did you encountered? I have gone through the process and might be able to help you.
nguyenson91hp said:
Did you get into issue rooting Proton? what exactly did you encountered? I have gone through the process and might be able to help you.
Click to expand...
Click to collapse
No it wasn't that. I flashed the 3 files for the kernel (I'm not rooted) and rebooted. That's when I went into boot loop. I didn't realize how to break out but eventually I got the right key and back to fastboot. From there it was easy. I'm at a point where I think the only way to change the kernel on ProtonAOSP is to be rooted. I don't really feel like going thru all the gyrations of rooting and patching for my banking app and GP to work. I'm not even thrilled that I'm unlocked but I can live with that for now. But thanks so much for your offer of rooting help. It's just not in the cards for me at this point. One thing I was pondering is if I can root, flash the kernel and then unroot. But I'm still licking my wounds over this one and thankfully I'll live to fight another day.
I see. I would imagine you should do that when you have another phone to back you up when things derail. It will be fun and more confident that way
I just realised you triggered this by trying to change kernel. I'm no expert but I'm thinking you are right - you prob need to to root to be able to successfully boot again.
Related
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
The phone was working great, other than the noise cancelling mic cancelling out my voice, but I thought since the update was available, I might as well do it. Once I got on ICS I was having quite a few issues: overall slower, delay in the screen turning on, hotter battery, longer time to charge, wallpaper would flash on before the HTC screen when booting up, there were more just can't remember right now.
I hear about the Global update and think it may fix some of the problems I was having, but they got worse. Now I still have everything I did before (except maybe the hot battery) Also have 3 new issues now: the screen doesn't come back on when I take it away from my ear during a call, browser goes white when going to a new page and I have to reload the page, can't post on any forums in the browser.
Here's the process I went through getting the Global (copied from another forum that I was updating as I was going)
I downloaded it from android police, got to step 6 of the directions, looked away from the phone to see what step 7 was. The phone vibrated and is now on the screen with the green down arrow and 2 in a circle around it. Says "Updating Software from Verizon Wireless" with a green progress bar. Hope I did it right.
That went through rebooted to HBOOT, pressed vol. up twice. It checked everything. Rebooted. Pressed. Vol. up to install. Upadated everything. Pressed power to reboot.
Took a little while on the white HTC screen, now says "Andoid is upgrading..." "Optimizing application [some number] of 77." I think I did it right.
Just checked and everything is right. Woo-Hoo! Not that I'll ever use global, I was hoping it may have fixed some of the bugs I was having, but no
Also of note, I didn't pull the battery. My case is hard to get off, so I just turned off fast boot and that worked.
Click to expand...
Click to collapse
What do I do at this point? My phone is getting less usable by the day as I keep noticing all these bugs.
Wipe your phone clean and use the RUU that android police posted today to install the latest patched OTA clean. That's what I'd try anyway.
I'll try that in the morning, thanks. Hopefully all goes smoothly. Still learning how to do things (afraid of rooting, but that's another thread)
VooDooCC said:
I'll try that in the morning, thanks. Hopefully all goes smoothly. Still learning how to do things (afraid of rooting, but that's another thread)
Click to expand...
Click to collapse
There are plenty of knowledgeable members here to walk you through it if you just shoot someone a pm. It's all very simple.
As for your problem, try the ruu hopefully that works I'm not sure about the mic canceling out your voice that might be a hardware problem let's hope not
Sent from my ADR6425LVW using xda app-developers app
Stupid person time (I don't believe there are stupid questions)
By "wipe phone clean" then flash the RUU. I get the flashing part, but what do you mean by wipe clean. Is there another step in there or does it automatically happen when flashing? I've only been in recovery once, so I didn't really study the options. On my D2, there was a wipe option.
VooDooCC said:
Stupid person time (I don't believe there are stupid questions)
By "wipe phone clean" then flash the RUU. I get the flashing part, but what do you mean by wipe clean. Is there another step in there or does it automatically happen when flashing? I've only been in recovery once, so I didn't really study the options. On my D2, there was a wipe option.
Click to expand...
Click to collapse
The RUU should wipe it but you can go into recovery and wipe /data and /system to remove the current rom.
Making sure I got all this right, but won't be trying until tomorrow afternoon. Only at 40% charge and going out of town in the morning and need the phone.
1. Rename the Android Police download to PH98IMG.zip and copy to sd card (don't have to extract anything out like I did on the .1)
2. Boot into recovery (vol. down and power)
3. Let it start flashing (If it starts automatically, how do I get to the wipe /data and /cache options?) I know it should be wiped auto. but I want to do it myself to make sure.
4. Pray to Andy that there's no bugs this time.
You need to boot into bootloader, not recovery, that will happen when you do the battery pull then start it volume down + power. I'm pretty sure the RUU will wipe everything so you should be good.
Problem with newest ICS
The new ICS has a problem with the browser. Links are squirrelly when touched; sometimes
no reaction, sometimes checks every box on the page. Just does not feel right when moving
around on web pages.
Seems ok to me, I'd recommend Chrome over stock unless you need Flash support anyway.
Sorry, I got the terms confused on the terms. I knew it was vol. down and power though
I finally got around to flashing the RUU, all is well so far, will report back if anything changes.
I'm s-off but my bootloader is unlocked. Do I need to relock the bootloader before flashing the RUU.
Sent from my ADR6425LVW using xda app-developers app
There is a tradition on rezounds to always install an RUU two times in a row, then let it boot up normally before installing custom things like hboots, recoveries, or ROMs.
I used to read posts of people saying that it must be done twice to assure everything gets installed right, and to avoid problems.
So, I recommend doing the ruu twice in a row, especially if your phone was not stock beforehand.
Howard
p.s. my favorite browser is opera mobile.
If s-off and unlocked, there is no need to relock to install an RUU.
Turns out I got a little too anxious. I thought stuff was working, but that was just because I was thankful that I installed the RUU right, still new to this. Still having all the same problems though
When you say install twice in a row, should I just try installing it once again tomorrow or twice since I downloaded an app or two?
Also, you say twice, then boot up normally, when I installed this it just booted up after the install was finished. Is there a way to install it again before it boots for the first time?
method
Make sure the Android Police 3.14.605.12 renamed PH98IMG.zip on your sdCard.
Boot up with Volume down, Power to get into hboot. It will ask your permission with a
Volume up and then run the update. I think they mean after 1st boot, answer English,
and get out of setup with No and default until steady. Do a factory reset in Settings,
Storage and boot up again. Then shut her off again and restart as previously to run that
PH98IMG.zip again.
After the next boot up, insert actual information like Google etc. to start Google Play
and fetch your favorite apps. Then you're running 100% stock.
noticed the same thing with in calls. Pull the phone away from your ear and the screen should come back on, but it seems delayed. I usually have to tap the power button twice to get the screen back on.
Running simplistic 3.0 which is based on the newest leak, after flashing the leak.
FWIW I have the issue with the screen not coming back on after pulling the phone away form your ear as well, however I'm on the ICS OTA, not the global.
I never had the problem on the ICS OTA, but I also only had that for a couple of days before getting the global (.1) from Android Police.
In the process of doing the second flash. As per michaels instructions.
I went to Verizon yesterday and tried seeing about exchanging the phone, since it's having all these problems, and was told no. That it's so common and pretty much every phone has the same things, so it's considered to be working and I just have to wait on a patch. He then told me that if I wanted I could void my warranty and s-off it to go back to GB. I found that kind of odd. Then he tried pushing the Razr on me, I said no I like HTC so then he told me that the Droid 4's are having the same problems too.
Hi guys I need some urgent help. I'm wanting to go back to stock recovery so I can install OTA updates when they are available. I made the mistake of rooting my phone without thinking about updates. I just want it back to stock so it's all nice and easy to use and I don't need to worry. I've found this thread which contains the stock recoverys but when I try and flash the STOCK RECOVERY 1.54.206.5 file I can't even into recovery and just got a error symbol up.
My phone is on the o2 network (I'm in the UK) and my phone is 4.4.2 Software number 1.54.206.5. Am I right in thinking it is that file I need?
If someone could take 5 minutes of their time to help me out it would be ever so much appreciated
EDIT - When Ive sent the stock recovery and I go to boot into it the symbol is a phone with a warning sign. Is that just what it is suppose to do or is it because it's wrong? I read on the thread "You can test originals by flashing them. If you see a phone with warning sign it's the HTC original one."
PLEASE HELP!
Nah, that's how it looks stock. You have to play around with some of the buttons to get the reset and reboot options to pop up. I can never remember what to do exactly. Try hitting the the Volume Up + Power on that screen. But I don't think they change the recovery much if at all between updates.
es0tericcha0s said:
Nah, that's how it looks stock. You have to play around with some of the buttons to get the reset and reboot options to pop up. I can never remember what to do exactly. Try hitting the the Volume Up + Power on that screen. But I don't think they change the recovery much if at all between updates.
Click to expand...
Click to collapse
Ohh yes brilliant! . I panicked and thought it meant it couldn't find a suitable recovery to boot into. It's all sorted now and hopefully I will have no problem installing OTA updates when they become available. Thank you
No problem. Glad all is well.
Alright, so I have a big problem.
It all started with me making Nova into a system app and uninstalling the native Huawei launcher (very ugly). I realized I had made a mistake when I found out I was now unable to change between launchers, even upon making Google Now launcher, which I also use, a system app as well through an app called Link2SD. Now, I backed up my /system, /data, /recovery etc with TWRP, and decided to uninstall nova and install google now into /system through ADB. I followed online guides as noted, but now the phone won't boot.
More correctly, the phone will boot, show Huawei's initial logo, then go to bootanimation, and either get stuck there or go to the "EMUI Optimizing..." screen and get stuck at 98% (It's probably since Google Now wasn't properly installed so there's no launcher to boot the phone with). I said alright, let's restore the NANDroid backup. Rebooted phone, Vol.Up key to enter recovery - only to be greeted by Huawei eRecovery, and no TWRP. This is extremely odd since I didn't do anything (I believe) that would delete TWRP.
I can't post links yet I think, but if it helps, I followed AndroidAuthority's post on installing apps as system apps, and a forum on AndroidCentral for uninstalling Nova.
There are 3 options in the recovery - Reboot (won't help, I guess), Shutdown, and "download latest version and recovery". I would normally go with this and pray for a wiped, but working Honor 5X, but I remember reading somewhere on here that you can't install a system version after you've done certain things. I can't find the specific post, but I'd rather make a post of my own and get help than try to install the stock system and get bricked.
Last thing, and the reason why I didn't reflash TWRP or something like that - my computer won't recognize the device in this recovery. All I get when I connect the device is a new partiton listed as "CD Drive (E: )" on My PC.
What can I do?
Have you tried holding Volume Up+Volume Down+Power (TWRP)? Or Volume Down+Power(Fastboot)? See if that gets you anywhere. Eventually as long as you can get into TWRP, you can restore.
If not, Doublecheck Device Manager in Windows to see if your computer is having trouble recognizing the device at all (yellow exclamation). Install ADB drivers if that is the case (When your phone is in fastboot, windows sometimes doesn't use that same ADB driver).
Hutch MD said:
Have you tried holding Volume Up+Volume Down+Power (TWRP)? Or Volume Down+Power(Fastboot)? See if that gets you anywhere. Eventually as long as you can get into TWRP, you can restore.
If not, Doublecheck Device Manager in Windows to see if your computer is having trouble recognizing the device at all (yellow exclamation). Install ADB drivers if that is the case (When your phone is in fastboot, windows sometimes doesn't use that same ADB driver).
Click to expand...
Click to collapse
THANK YOU! Vol up + Down + Power did the trick for booting into TWRP. Currently copying the NANDroid backup to my honor and restoring it right away. I must ask - is there a specific reason the key combination was different this time? Is there a foolproof combo for booting into TWRP? Only phone I had rooted besides this one was a Moto G 2013, and it booted into ñTWRP without fail by pressing Vol Down+Power...
ElBerretin said:
THANK YOU! Vol up + Down + Power did the trick for booting into TWRP. Currently copying the NANDroid backup to my honor and restoring it right away. I must ask - is there a specific reason the key combination was different this time? Is there a foolproof combo for booting into TWRP? Only phone I had rooted besides this one was a Moto G 2013, and it booted into ñTWRP without fail by pressing Vol Down+Power...
Click to expand...
Click to collapse
I couldn't tell you. This phone can be a little weird with the button combinations. For example, Volup+Power gets me into TWRP most of the time. I'm glad you are on your way back to a functional phone!
Hutch MD said:
I couldn't tell you. This phone can be a little weird with the button combinations. For example, Volup+Power gets me into TWRP most of the time. I'm glad you are on your way back to a functional phone!
Click to expand...
Click to collapse
Yeah, I realize. When I booted to stock recovery instead of TWRP using the same button combination I always use I got worried - I didn't even know the stock recovery was still installed on the phone. Guess I'll stick with this launcher until fingerprint suppport allows me to flash a custom ROM. Thanks again!
ElBerretin said:
Yeah, I realize. When I booted to stock recovery instead of TWRP using the same button combination I always use I got worried - I didn't even know the stock recovery was still installed on the phone. Guess I'll stick with this launcher until fingerprint suppport allows me to flash a custom ROM. Thanks again!
Click to expand...
Click to collapse
I would still recommend trying out CM13. It's a huge performance boost and overall better experience. If you don't like it, you can always restore from your Nandroid backup, haha.
Hutch MD said:
I would still recommend trying out CM13. It's a huge performance boost and overall better experience. If you don't like it, you can always restore from your Nandroid backup, haha.
Click to expand...
Click to collapse
Yeah, maybe I'll try that. Do I have to wipe everything beforehand? And can I restore my /data partition after installing? I have lots of stuff in my phone and restoring/backing up by hand would be a pain... I'll still miss the fingerprint sensor, though.
Hutch MD said:
I would still recommend trying out CM13. It's a huge performance boost and overall better experience. If you don't like it, you can always restore from your Nandroid backup, haha.
Click to expand...
Click to collapse
Just got my Honor 5X yesterday (GR5 to be specific... KII-L21). I really want to try CM13 but i'm still lost on Huawei procedures lol. I'm familiar with Samsung and Sony as i have used those phones... Huawei, never... first time! Lol
I have neither rooted nor unlocked BL. Hoping someone helps me out so i can learn quickly and start helping others around here too
stanley08 said:
Just got my Honor 5X yesterday (GR5 to be specific... KII-L21). I really want to try CM13 but i'm still lost on Huawei procedures lol. I'm familiar with Samsung and SOny as i have used these phones... Huawei, first time.
I have neither rooted nor unlocked BL. Hoping someone helps me out so i can learn quickly and start helping others around here too
Click to expand...
Click to collapse
There are plenty of threads here. Yes, it will wipe everything on your phone. Follow the instructions from these threads.
First, you have to Unlock the Bootloader and install TWRP.
Then you flash CM13.
---------- Post added at 05:52 PM ---------- Previous post was at 05:47 PM ----------
ElBerretin said:
Yeah, maybe I'll try that. Do I have to wipe everything beforehand? And can I restore my /data partition after installing? I have lots of stuff in my phone and restoring/backing up by hand would be a pain... I'll still miss the fingerprint sensor, though.
Click to expand...
Click to collapse
Yeah, you'll have to do a full wipe. It'll be okay if you're rooted - Use Titanium Backup for all of your important apps/appdata; Use SMS Backup & Restore to load up all of your recent call history and texts; Back up your photos and other stuff by hand, at least, that's what I would do. Then make a Nandroid backup after you're done flashing/setting everything back up.
While trying to load a rom, I got a failed message, damn cat ran across the desk and it rebooted, I was to the point I should of flashed the overlay, did NOT make it that far. It boots up to the welcome screen, but I have no access to hit "start" as my touch screen is not working. Is it done for? I cant see it any longer in adb devices, so I cant continue where I left off. Linux cant see it at all. Windows knows its there. So it did not make a complete fash, it tried to reboot into stock i assume, looks stock. What can I do at this point? Any help would be great.
deleted
I got in. I can not enter fastbootd, and do not know where its saved. Can some one help me get my recovery back? I flashed a recovery backup, but it comes up witht he little dead andriod and no command error. I need to get to fastbootd. Any help would be wonderful.
If you can get into fastboot, isn't there a tool, LMSA rescue to bring back bricked device? wipes all data though.
Were you trying a custom ROM or stock? try booting to fastboot mode, power + vol-down, and fastboot flash the stock boot.img, can be found here: https://mirrors.lolinet.com/firmware/moto/sofia/official/
hope this helps. I just got the phone yesterday, soft bricked trying to flash magisk, flashed stock boot and was back in business. I was not using any type of custom rom though.
I was able to find stock boot and recovery images, which allowed me to just start over. Here is an screen shot of what would happen when flashing any ROM.
That's two different attempts. With two different errors.
On a crazy note, I ordered and got in the exact same phone off eBay, has lineage os, magisk, twrp. Now from what I've read, twrp can't be used to install ROMs yet. I've actually tried it on the problem phone we are working on here, but can't swipe with it. The screen is not correctly responsive. Yet this eBay phone, works great... Not sure how he did it. Id love to figure this out, I can't let it beat me.
klloyd said:
I was able to find stock boot and recovery images, which allowed me to just start over. Here is an screen shot of what would happen when flashing any ROM.
That's two different attempts. With two different errors.
On a crazy note, I ordered and got in the exact same phone off eBay, has lineage os, magisk, twrp. Now from what I've read, twrp can't be used to install ROMs yet. I've actually tried it on the problem phone we are working on here, but can't swipe with it. The screen is not correctly responsive. Yet this eBay phone, works great... Not sure how he did it. Id love to figure this out, I can't let it beat me.
Click to expand...
Click to collapse
I would try this next: https://support.lenovo.com/us/en/downloads/ds101291-rescue-and-smart-assistant-lmsa