Related
DISCLAIMER:
Your device, your responsibility. I am not liable for anything you flash, including this.
As a result you'll probably want to read the rest of the thread and at least be aware of what you're flashing.
You've been warned.
CM: CWM Based Recovery for SPH-L720 (jfltespr)
Features:
This is comes from CM as it is provided in the source repos. I will be keeping it as such at this time.
Only deviations are to allow it to build properly and are generally from CM repos.
If modifications deviate from CM source we will set up a new repo.
Screenshots: None
Latest Build: v1.0
Tar/ZIP Mirror: [CWM][RECOVERY]Team SXTP CWM for Galaxy S4 (Team SXTP Site)
Flash Instructions:
Boot to Odin Mode and flash via Odin.
Summary Changelog:
Code:
v1.0 - Final Prealpha, successful operations and display
Prealpha Builds - Initial Buildup.
Source:
CyanogenMod Official Repositories
Device Dependencies:
android_device_samsung_jf-common
android_device_samsung_msm8960-common
android_device_samsung_qcom-common
Sprint GS4 Device Repository
NOTE: Due to potential copyright issues I do not include a vendor repo.
You can extract the files from the phone or ROM as needed - should you decide to build on your own.
Credits:
Early Bringup Advice: Entropy512, Shabbypenguin, Cordell12
Current Advisors/Collaborators: Noobnl (CM CDMA Maintainer)
Testers: Mohogalore, robbyamor, crawj and others
Steve Kondik (Cyanogen) for CM development and jf common work
The CM maintainters who continue to improve CM along with Mr. Kondik
The crew that is Paranoid Android - Pure Hybrid!
...and of course! You, the community, for your support as well! Thank you!
Heard this has bad graphics so will revisit asap
Sent from my SPH-L900 using Tapatalk 2
garwynn said:
Heard this has bad graphics so will revisit asap
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Sorry for not reporting that here. Ever since I screwed up my phone I've been killing time by flashing every recovery firmware I got my hands on. I'll probably keep testing before the stock image comes out.
Running this now... as stated graphics do not redraw every other click but it does function normally otherwise. Just made a backup which completed normally.
edit... navigation is also a little touchy vol down will sometimes register as enter.
did a full wipe booted fine now to restore.
Thanks - working on a possible graphics fix at the moment.
Will post Alpha 4 when it's ready.
harrybozack said:
Sorry for not reporting that here. Ever since I screwed up my phone I've been killing time by flashing every recovery firmware I got my hands on. I'll probably keep testing before the stock image comes out.
Click to expand...
Click to collapse
Define screwing up the phone... just curious if can get it back running.
I have a stock ROM that is uploaded but will have to rename to pull from web.
restore completed and looks good
lafester said:
restore completed and looks good
Click to expand...
Click to collapse
Very nice! So you're functioning normally?
I will test this CWM to see how it works, i did test shabby penguins version and got a bug where it would only let me select every other selection and didnt recognize the selection.
Alpha 4 posted.
MoHoGalore said:
Very nice! So you're functioning normally?
Click to expand...
Click to collapse
yes everything restored that I can tell. navigating cwm is difficult though at the moment with the graphics error
same result on Alpha 3 for me. Will test Alpha 4
---------- Post added at 12:04 PM ---------- Previous post was at 12:00 PM ----------
just tested Alpha 4 and same results. Only lets me select every other selection and when i do make a selection the menu goes away and im left with the CWM logo and label on the bottom. Have to hold power to reboot.
when you have a blank screen hit vol down to enable the graphics
Sounds like need to play with recovery keys a little more. Glad it is functionally working though!
Sent from my SPH-L900 using Tapatalk 2
garwynn said:
Define screwing up the phone... just curious if can get it back running.
I have a stock ROM that is uploaded but will have to rename to pull from web.
Click to expand...
Click to collapse
Well it's stuck in a boot loop. I flashed recovery firmware for the i9505 instead of my model phone and one of them screwed up big time. My own fault for being careless.
lafester said:
when you have a blank screen hit vol down to enable the graphics
Click to expand...
Click to collapse
well i did that but then it goes to a loose root access type screen. i always check no but then it reboots.
garwynn said:
Define screwing up the phone... just curious if can get it back running.
I have a stock ROM that is uploaded but will have to rename to pull from web.
Click to expand...
Click to collapse
Wait so you have the stock rom for the SPH-L720? I'd love to try flashing that to fix my problems.
Alpha 4 works, except you need to count key presses. Every other press changes highlighted selection but every press registers for choice (if that makes sense.) When pressing enter to make selection, press volume down to "wake up" the screen.
Backup successful. Restore successful.
I can make a video if that would be easier to explain what I'm seeing, if needed.
:edit: Location for backup is normal - /data/media/clockworkmod/backups - Must have been something I did. Disregard previous statement.
MoHoGalore said:
Alpha 4 works, except you need to count key presses. Every other press changes highlighted selection but every press registers for choice (if that makes sense.) When pressing enter to make selection, press volume down to "wake up" the screen.
Backup successful. Restore successful.
I can make a video if that would be easier to explain what I'm seeing, if needed.
:edit: Location for backup is normal - /data/media/clockworkmod/backups - Must have been something I did. Disregard previous statement.
Click to expand...
Click to collapse
You had the same experience as I did. Worked fine just hard to navigate.
In other news I just activated my phone and it did a factory reset and installed on the sprint crap. It did not wipe sd so my backup is still there. attempting to restore now.
update: restore successful
Update with Alpha 4 and testing of Garwynn's test builds: Actions taken in this order;
(Started with Alpha 4 already flashed)
1. Backup - Successful
2. Restore - Successful
3. Flashed Stock Dump Recovery - Successful
4. Flashed Stock Dump Kernel - Successful
5. Flashed Stock Dump Rom - Successful
6. Flashed Alpha 4
7. Performed Wipe Data/Factory reset- successful
8. Rebooted system
9. Restored previous backup - Successful
(Used Odin 1.85 for Stock build flashes)
Hey folks. I've tried every search here & via Google that I can think of and the answer won't come to me. Here's the weird, surreal, but I assure you very current problem. I screwed around trying to install Jasmine 5.0 and it has bitten me in the rear-end. In order to fix a problem I had with it, I wanted to KDZ back to stock and start over. Unfortunately it won't let me do that. When I try to go into Download mode, it gives me a secure boot error, turns the screen black and flashes the LED at me multicolor-style. The only way to get out of that is a battery pull.
I can boot into Recovery just fine. I'm back on SkyDragon 4.4 as we speak, but not being able to get into download mode is what I'd consider a BIG PROBLEM, considering that's how you fix soft bricks. If I ever have a problem, I'm toast. Thus, my flashing days are pretty well over unless I can get this fixed.
I did find this from @bweN diorD :
bweN diorD said:
well it should be the aboot then. while testing, the only things that gave me a secure boot error were boot (which i just gave you) and aboot.
im not sure how you would install aboot, i dont have a flashable zip. maybe using terminal in twrp, but i have little experience to give advice on that.
Click to expand...
Click to collapse
Does that mean I need to figure out how to get 12B aboot & boot properly restored from the img thread? If so, does anybody know HOW one might do that? I apologize, but I'm VERY much at my wit's end here and can't figure it out right now. Any help at all would be greatly appreciated.
EDIT - FIXED!
annoyingduck said:
Download mode fixed, @hsbadr will be along momentarily with a file to flash the same way you did J-5
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
Go here for download mode fix: http://forum.xda-developers.com/showpost.php?p=59357420&postcount=2237
Don't forget to delete the previous images from your internal sd
Works perfectly, just tested
Click to expand...
Click to collapse
From what I've seen told to other people in the same situation, you need to flash the laf.img, but you'll have to look up how to do that. Probably via adb connected through TWRP? Shrug. Good luck dude, sorry to hear.
Sent from my VK810 4G
There may be a kind person that has a solution. If whatever it is works (he's busy right now), I'll definitely post it here and make it as searchable as possible!
roirraW "edor" ehT said:
From what I've seen told to other people in the same situation, you need to flash the laf.img, but you'll have to look up how to do that. Probably via adb connected through TWRP? Shrug. Good luck dude, sorry to hear.
Sent from my VK810 4G
Click to expand...
Click to collapse
My thoughts exactly, I'll go over that with him, just want to check a few things first.
hokiealumnus said:
There may be a kind person that has a solution. If whatever it is works (he's busy right now), I'll definitely post it here and make it as searchable as possible!
Click to expand...
Click to collapse
How are you going about booting into download mode?
annoyingduck said:
How are you going about booting into download mode?
Click to expand...
Click to collapse
Power off, hold volume up & plug in USB cable.
hokiealumnus said:
Power off, hold volume up & plug in USB cable.
Click to expand...
Click to collapse
Ok, I'm showing the same symptom. Let me test on my device first. give me a few min
annoyingduck said:
Ok, I'm showing the same symptom. Let me test on my device first. give me a few min
Click to expand...
Click to collapse
I've a possible fix... hangouts
just checked to see if i have that issue...ive got everything working fine here...running JasmineROM v5.0 and never had a boot signature error...until...just for the heck of it tried download mode and low and behold my download mode give me that error...
+1 on the secure boot error in download mode. Much appreciated when you guys develop a fix if you could post it here.
jdgesmlls said:
+1 on the secure boot error in download mode. Much appreciated when you guys develop a fix if you could post it here.
Click to expand...
Click to collapse
Working on it with the man himself, just need some testing time...
annoyingduck said:
Working on it with the man himself, just need some testing time...
Click to expand...
Click to collapse
Let me know if you need anyone to test stuff, I am up and running, can get into recovery and restore but again as stated if .tot is required I am in the same boat....
No worries, take all the time you need. Thankfully our devices are working.
We should probably just hold off on our flashing addiction until it's fixed.
hokiealumnus said:
No worries, take all the time you need. Thankfully our devices are working.
We should probably just hold off on our flashing addiction until it's fixed.
Click to expand...
Click to collapse
Yes, definitely... I am fully functional, can make calls and such so your work and expertise is much appreciated!
Download mode fixed, @hsbadr will be along momentarily with a file to flash the same way you did J-5
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
Go here for download mode fix: http://forum.xda-developers.com/showpost.php?p=59357420&postcount=2237
Don't forget to delete the previous images from your internal sd
Works perfectly, just tested
annoyingduck said:
Download mode fixed, @hsbadr will be along momentarily with a file to flash the same way you did J-5
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
Go here for download mode fix: http://forum.xda-developers.com/showpost.php?p=59357420&postcount=2237
Don't forget to delete the previous images from your internal sd
Works perfectly, just tested
Click to expand...
Click to collapse
So I have already restored back to Illusion, and I did that because I was getting an LGSmartCover FC in J-5 once I booted up. Can I flash this in recovery and keep my current setup or do I have to go through the install of J-5 again.
Again, thanks for the quick turnaround on this...
EDIT*** I think nevermind, I thought about it for a minute and just use the same install instructions but replace the contents of FixDownloadMode.zip??
annoyingduck said:
Download mode fixed, @hsbadr will be along momentarily with a file to flash the same way you did J-5
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
Go here for download mode fix: http://forum.xda-developers.com/showpost.php?p=59357420&postcount=2237
Don't forget to delete the previous images from your internal sd
Works perfectly, just tested
Click to expand...
Click to collapse
Works like a charm! Thanks to you both - @hsbadr & @annoyingduck !!!! We would have been in a heck of a bind without your help.
you can flash this on anything....when we were testing J-5 we got a little over protective and decided to upgrade what the new download mode fix script installs to 23b images, which conflict with bumped recoveries. It didn't need to be done, so you should do this repair if you flashed J-5 either way - no matter what current rom your on, it won't effect anything other than download mode. Next J-5 will fix it for everyone. Basically bump requires KK aboot. Download mode requires aboot to match rpm,tz,and laf. Once those get upgraded to LP, download mode fails because of the bumped aboot. Turns out, we didn't need those images to get LP booting, so fixes are in the future.
annoyingduck said:
you can flash this on anything....when we were testing J-5 we got a little over protective and decided to upgrade what the new download mode fix script installs to 23b images, which conflict with bumped recoveries. It didn't need to be done, so you should do this repair if you flashed J-5 either way - no matter what current rom your on, it won't effect anything other than download mode. Next J-5 will fix it for everyone. Basically bump requires KK aboot. Download mode requires aboot to match rpm,tz,and laf. Once those get upgraded to LP, download mode fails because of the bumped aboot. Turns out, we didn't need those images to get LP booting, so fixes are in the future.
Click to expand...
Click to collapse
That worked perfect!
Thanks @hsbadr, @annoyingduck!! as always, great work!!
annoyingduck said:
you can flash this on anything....when we were testing J-5 we got a little over protective and decided to upgrade what the new download mode fix script installs to 23b images, which conflict with bumped recoveries. It didn't need to be done, so you should do this repair if you flashed J-5 either way - no matter what current rom your on, it won't effect anything other than download mode. Next J-5 will fix it for everyone. Basically bump requires KK aboot. Download mode requires aboot to match rpm,tz,and laf. Once those get upgraded to LP, download mode fails because of the bumped aboot. Turns out, we didn't need those images to get LP booting, so fixes are in the future.
Click to expand...
Click to collapse
ok do i have to do a clean flash of jamison5.0 before i flash the fix or can i do a factory reset nd then flash the fix via twrp adb?
nevermind...i just rebooted to recovery and flash...download mode work and didnt have to reflash rom thanks @annoyingduck @hsbadr i was scared here because flashings an addiction
For the download mode fix you shouldn't need to factory reset. Heh, when I used it I was back on KK, booted into recovery, flashed the fix and rebooted straight back into the ROM.
Installing now...
having a problem reinstalling TWRP. I followed all the commands and here is a copy of what Happens when I flash
C:\Users\Robert\Desktop\files\TWRP_for_mate2\TWRP_for_mate2>fastboot flash recovery twrp.img
target reported max download size of 804257792 bytes
sending 'recovery' (14382 KB)...
OKAY [ 0.469s]
writing 'recovery'...
OKAY [ 0.328s]
finished. total time: 0.797s
but when I try to boot into it it starts up the stock recovery. Any suggestions on how to install TWRP and make it stick or how to gain root because I mainly use TWRP for root.
I also get this screen sometimes when trying to boot into boot loader. The phone doesn't seem to vibrate like it does when it boots normally or loads recovery and boot loader.
http://imgur.com/IQlBmP1
The usb is connected but I haven't tried to send anything to the phone or told anything other than to reboot system when it boots into stock recovery. If I leave it , it just sits there doing nothing so I rebooted and it boots just fine. Should I try to reflash stock recovery and then flash TWRP?
Found a way to at least let the phone get using TWRP without apparently being able to boot into it for some reason. Don't know if you can backup and restore backups using this method but at least its a temporary workaround. I found it at this site https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/. below is the guide copied from the site.
Prerequisites
•An unlocked bootloader – It is just a command away on Nexus devices. Google will give you very useful links depending on your device type.
•ADB with Fastboot – Check out this link: http://www.jailbreakeye.com/android/install-adb-fastboot
•A custom recovery image – TWRP or CWM (check the Download recovery or Download touch recovery columns)
Guide
1.Copy the downloaded recovery image (.img file) to the folder where you have placed your ADB and Fastboot.
2.Launch terminal (or command prompt on Windows).
3.Navigate to the directory where you have placed the ADB, Fastboot and .img file together.
4.Shut down your phone and reboot into boot loader. For nexus devices, simply hold volume down + power to start up the phone.
5.Connect your phone to your computer.
6.On terminal (or command prompt) window, write fastboot boot <img file name>, e.g. fastboot boot twrp.img.
7.Your phone will restart and will boot into the recovery mode.
That’s it. As simple as it can get!
Hopefully this will help out those who are having trouble getting into TWRP after updating to B321.
what new on the b321 updated
dizwikedcbr said:
what new on the b321 updated
Click to expand...
Click to collapse
It's very stable. Lots of things are now fixed. Getting 3rd party launcher to stick after reboot is now working. Actually, I have been using it as my daily driver for several days. Not even rebooted since install. This may be released to public, at least as the next preview.
Which launcher?
kimtyson said:
It's very stable. Lots of things are now fixed. Getting 3rd party launcher to stick after reboot is now working. Actually, I have been using it as my daily driver for several days. Not even rebooted since install. This may be released to public, at least as the next preview.
Click to expand...
Click to collapse
Which launcher are you using?
I installed B321 ...phone rebooted and is stuck on huawei logo screen. I can't get to fastboot or recovery. Help.
kimtyson said:
It's very stable. Lots of things are now fixed. Getting 3rd party launcher to stick after reboot is now working. Actually, I have been using it as my daily driver for several days. Not even rebooted since install. This may be released to public, at least as the next preview.
Click to expand...
Click to collapse
Nope. Still quite a few issues with notifications, led issues and issues with losing APN settings at random requiring a reboot. Sounds like you've just been lucky.
Have to consider user error. How many of those having issue are stock. Not rooted and LCD density changed etc. Not all issues are the fault of the rom. I am sure Huawei is taking that into consideration.
gale2000 said:
I installed B321 ...phone rebooted and is stuck on huawei logo screen. I can't get to fastboot or recovery. Help.
Click to expand...
Click to collapse
same happened with me. did the b321 ota and got stuck on boot screen. had to go back to b309 and now cant get back to b320.
How long did you let it run. It can take a good while on first boot...
I let it sit there so long i had forgotten about it all together. so at least 10-15 min on huawei splash screen. not the emul loading screen. i dont think a 30-40mb upgrade should take longer that it takes to load a complete image
---------- Post added at 01:17 AM ---------- Previous post was at 01:16 AM ----------
And when i search for updates now I get nothing... stuck on b309 i guess.
Moody66 said:
Have to consider user error. How many of those having issue are stock. Not rooted and LCD density changed etc. Not all issues are the fault of the rom. I am sure Huawei is taking that into consideration.
Click to expand...
Click to collapse
My phone is stock. Nothing added and no root. The issues are apparent and have been reported by other users, so the issues I have posted are NOT user error. A number of them have been confirmed as being fixed in the next release. 321 won't be the next release to the general public.
Confirmed fix in next release? Who is running the "next release"?
The b321 ota might be a good thing, but it's new enough that I am wary. I just upgraded to b320 less than a week ago and still haven't gotten everything situated on the phone. I've had some issues with Nova Prime launcher on power up. I have one question, er maybe two. What improvements if any make this new update a good choice and will I once again have to reload everything back onto my phone?
Moody66 said:
How long did you let it run. It can take a good while on first boot...
Click to expand...
Click to collapse
Overnight. If I power it off it turns itself right back on. Still stuck on splash screen...can't get to fastboot or recovery. Boo.
gale2000 said:
Overnight. If I power it off it turns itself right back on. Still stuck on splash screen...can't get to fastboot or recovery. Boo.
Click to expand...
Click to collapse
You have to put b320 or 309 update on the root of your sd card in folder named dload. do the three finger reset ( vol + vol- and PWR ) it will then install b320.
My guess is that you were still rooted when you updated, you have to be stock.
Davinci50 said:
You have to put b320 or 309 update on the root of your sd card in folder named dload. do the three finger reset ( vol + vol- and PWR ) it will then install b320.
My guess is that you were still rooted when you updated, you have to be stock.
Click to expand...
Click to collapse
Yes, I was rooted. Thanks for your help.
Harris.S.Newman said:
Which launcher are you using?
Click to expand...
Click to collapse
I am using Nova but Apex also stuck after reboot.
gale2000 said:
I installed B321 ...phone rebooted and is stuck on huawei logo screen. I can't get to fastboot or recovery. Help.
Click to expand...
Click to collapse
Sorry for your headaches. I have had no issues but I am using a clean install with no root or other magical add-ons.
TheIgster said:
Nope. Still quite a few issues with notifications, led issues and issues with losing APN settings at random requiring a reboot. Sounds like you've just been lucky.
Click to expand...
Click to collapse
You are correct about the notifications but that is an EMUI thing and they have no intentions (so far) of changing EMUI, so deal with it or get a notification add-on app. (Sorry for my bluntness.)
What LED issues?
My APN has been perfect. I am on ATT. Not sure what your APN issue might be but I'm not seeing others with APN issues.
No reboots for me and no need for reboots.
So, yeah, I'm lucky I guess. Or maybe I have a clean install without root. Or maybe I just know what I'm doing.
Moody66 said:
Confirmed fix in next release? Who is running the "next release"?
Click to expand...
Click to collapse
Confirmed on the Huawei website I've been posting on as well.
kimtyson said:
You are correct about the notifications but that is an EMUI thing and they have no intentions (so far) of changing EMUI, so deal with it or get a notification add-on app. (Sorry for my bluntness.)
What LED issues?
My APN has been perfect. I am on ATT. Not sure what your APN issue might be but I'm not seeing others with APN issues.
No reboots for me and no need for reboots.
So, yeah, I'm lucky I guess. Or maybe I have a clean install without root. Or maybe I just know what I'm doing.
Click to expand...
Click to collapse
Notifications were working fine on JB. There are issues since the update that need to be addressed. EMUI had it working just fine prior to the update to L.
There are no LED notifications for some notifications at times and I have yet to get a notification via the LED for Facebook. With and without a third party app.
The APN issues are documented and reported by other users. It is being fixed in the next release.
My install, yes, was not clean, but only an upgrade from 309. I have never had root. Yes, of course, you and Moody are experts and the rest of us are idiots. You both sure like to insinuate that in your posts. It's a little tiresome, but if it makes you feel better, I guess feel free.
i found this trwp recovery floating around i dont know who made it.
it boots fine but no touch screen hopefully someone can fix it
https://www.androidfilehost.com/?fid=457095661767138152
kvip60 said:
i found this trwp recovery floating around i dont know who made it.
it boots fine but no touch screen hopefully someone can fix it
https://www.androidfilehost.com/?fid=457095661767138152
Click to expand...
Click to collapse
What's the easiest way to install this?
I didn't install it I just used" fastboot boot image-name"
kvip60 said:
I didn't install it I just used" fastboot boot image-name"
Click to expand...
Click to collapse
Ok Thanks. I am in and generating a backup. The touch screen was working for me mostly. It won't let me select Micro SDCard to save my backup.
Yeah like I said it need some repair I am pretty sure the mount points aren't perfect and I didn't compile it I had to use an otg and mouse to navigate
kvip60 said:
Yeah like I said it need some repair I am pretty sure the mount points aren't perfect and I didn't compile it I had to use an otg and mouse to navigate
Click to expand...
Click to collapse
What I did to navigate was I had to push the power button then it would bring the screen up where you can swipe the bottom to unlock the screen and use touchscreen. Navigating the storage was odd because it shows it is stuck on Internal storage, but If i click on SDCard, it will take me to that directory. I hope there is a nice update to this is the near future, so we don't have to access it through "adb reboot recovery"
You can flash it if you like I just don't trust this copy yet waiting for an update before I flash it
You can use" fastboot flash recovery twrp.img" to flash rather than "fastboot boot twrp.img " to boot it
kvip60 said:
You can flash it if you like I just don't trust this copy yet waiting for an update before I flash it
You can use" fastboot flash recovery twrp.img" to flash rather than "fastboot boot twrp.img " to boot it
Click to expand...
Click to collapse
Oh man you were so right. I had it flashed and it caused me all kinds of problems, like booting the screen upside down etc. I was finally able to find the recovery.img in another thread and get back the stock recovery. I think I will also wait until there is a more stable TWRP version.
I always use boot to test and I always backup my recovery before flashing because I had that happen to me before
Any idea on when a decent working custom recovery will be available?
blahforme said:
Any idea on when a decent working custom recovery will be available?
Click to expand...
Click to collapse
Probably when someone will have the will & time to work on it.
Maybe you'd like to take on this topic?
Lol. I hear you. I have very little understanding of Linux I have tried to make one but there aren't enough information about compiling device /vendor tree for a new device to go on
Just visit this page and you will get TWRP for Z016D. It's a Taiwan website with Chinese but you can see the blue link marked as "TWRP" and there you are.
https://www.asus.com/zentalk/tw/thread-214217-1-1.html
lssong99 said:
Just visit this page and you will get TWRP for Z016D. It's a Taiwan website with Chinese but you can see the blue link marked as "TWRP" and there you are.
https://www.asus.com/zentalk/tw/thread-214217-1-1.html
Click to expand...
Click to collapse
Thanks for this. Posting the Mega so people don't have to make an Asus account to grab it.
https://mega.nz/#F!EkFF1CJD!C8o2wXMARW3YJFOipDttbA
The 20170218 recovery works perfectly with my phone (6/64gb, 820). The first one posted in the OP worked, but was a bit glitchy. The updated one has working SD reading and touchscreen works without having to lock it first.
Could someone please tell me why twrp is booting upside down on my device, and how do I fix it? I just tried to run it in fastboot boot twrp-3.0.3-0-Z016D-20170218.img and once again it loads upside down, however the touch screen is where it normally is suppose to be, which makes it very difficult to navigate the menus. It is very frustrating. This has happened to me multiple times this week. I can't seem to get it to boot/load properly.
blahforme said:
Could someone please tell me why twrp is booting upside down on my device, and how do I fix it? I just tried to run it in fastboot boot twrp-3.0.3-0-Z016D-20170218.img and once again it loads upside down, however the touch screen is where it normally is suppose to be, which makes it very difficult to navigate the menus. It is very frustrating. This has happened to me multiple times this week. I can't seem to get it to boot/load properly.
Click to expand...
Click to collapse
Are you using the Snapdragon 821 version by any chance? Cause people with the s820 seem to be working fine.
I am using 821 my screen is flipped and no touch even after locking it
Huffy1 said:
Are you using the Snapdragon 821 version by any chance? Cause people with the s820 seem to be working fine.
Click to expand...
Click to collapse
No, I am using the sd820.
---------- Post added at 08:25 PM ---------- Previous post was at 08:07 PM ----------
I really don't want to wipe everything and start all over from scratch because everything else is working great right now. I guess if there is no easy solution, then I will just leave it alone. I ran it with fastboot and then made a backup and saved it on my microSD card. But I am worried if I wipe everything and start all over again, then I will have to call my bank again to verify my cards for Android pay. I am running the stock firmware version 1698, with stock recovery, an unlocked bootloader, & rooted. Also have Magisk & Titanium Pro installed, and I verified that Andoid pay works for me. (I already bought something using Android pay).
blahforme said:
No, I am using the sd820.
---------- Post added at 08:25 PM ---------- Previous post was at 08:07 PM ----------
I really don't want to wipe everything and start all over from scratch because everything else is working great right now. I guess if there is no easy solution, then I will just leave it alone. I ran it with fastboot and then made a backup and saved it on my microSD card. But I am worried if I wipe everything and start all over again, then I will have to call my bank again to verify my cards for Android pay. I am running the stock firmware version 1698, with stock recovery, an unlocked bootloader, & rooted. Also have Magisk & Titanium Pro installed, and I verified that Andoid pay works for me. (I already bought something using Android pay).
Click to expand...
Click to collapse
How did you install Magisk having stock recovery? Using the in-app installation?
---------- Post added at 01:08 PM ---------- Previous post was at 01:05 PM ----------
It seems @EypCnn is the developer of this TWRP builds...
sebastiandg7 said:
How did you install Magisk having stock recovery? Using the in-app installation?
Click to expand...
Click to collapse
I flashed Magisk v11.1 with TWRP, then installed Magisk Manager from the Google Play Store, after I rebooted my device. I did that by booting in to TWRP with fastboot to flash the .zip file. I did not flash TWRP to install Magisk.
My phone is 10 months old and began bootlooping a few hours ago. I've kept it in a bootloop but it never booted neither system nor recovery.
It's still under warranty but I'll keep it a few days to try a few things. I'm going on vacation next week so I'll be without phone 10 months is just unacceptable from a QA point of view from Huawei and Google. Anyway...
Up to now I get mixed results: I can boot in recovery but can't fully boot. I'll try a few others way (either kernels or parameters) later during the weekend and update this post.
Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is to limit the kernel to use less cores.
If your device is affected by the Boot Loop Of Death, you might try flashing this image to backup your data.
Twrp image:
twrp_3.1.1-bootloop (four cores)
Source code - Local manifest
https://github.com/architek/omnirom-twrp-angler_local-manifest
How to flash:
Reboot into bootloader mode (hold power + volume down)
unzip
fastboot flash recovery omni-7.1-twrp_3.1.1-bootloop.img
Feedback:
Tell me if that works out for you. Thanks.
Update
14th August : Binary link
21th August : Source code link
rchtk said:
My phone is 10 months old and began bootlooping a few hours ago. I've kept it in a bootloop but it never booted neither system nor recovery.
It's still under waranty but I'll keep it a few days to try a few things. I'm going on vacation next week so I'll be without phone 10 months is just unacceptable from a QA point of view from Huawei and Google. Anyway...
Up to now I get mixed results: I can boot in recovery but can't fully boot. I'll try a few others way (either kernels or parameters) later during the weekend and update this post.
Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is limiting the kernel to use 1 cpu.
Urls:
Xtwrp-3.1.0-0-angler.img
Xboot-opp3.170518.006-0bc919b4.img
How to use:
Reboot into bootloader mode (hold power + volume down)
fastboot boot Ximage.img
Will boot you either in recovery or system depending on the image you use.
Feedback:
Tell me if that works out for you. Thanks.
Click to expand...
Click to collapse
The best thing to do is to follow this method at either step 9 or step 10. https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
DEVILOPS 007 said:
The best thing to do is to follow this method at either step 9 or step 10. https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Explain how it is better than what I posted.
rchtk said:
Explain how it is better than what I posted.
Click to expand...
Click to collapse
Because you didn't share what link you were using information from and you didn't say that you tried following everything like flashing the system, boot, recovery, bootloader, vendor etc as that is what needed to fix bigger bricks. Also, you didn't take into account different factors like some things might not work making your method impossible. I'm not saying your method won't work for that certain situation but the link I posted is to one of the biggest people on xda as far as I know with an almost foolproof plan to fix bricks unless it is the blod.
DEVILOPS 007 said:
Because you didn't share what link you were using information from and you didn't say that you tried following everything like flashing the system, boot, recovery, bootloader, vendor etc as that is what needed to fix bigger bricks. Also, you didn't take into account different factors like some things might not work making your method impossible. I'm not saying your method won't work for that certain situation but the link I posted is to one of the biggest people on xda as far as I know with an almost foolproof plan to fix bricks unless it is the blod.
Click to expand...
Click to collapse
Yes, obviously, my post is for people experiencing blod. If you don't then you don't need these images.
The recovery image is not even flashed, its executed in RAM and allowed me to access my filesystem.
The system image goes up to moving dots but doesn't finish booting.
rchtk said:
Yes, obviously, my post is for people experiencing blod. If you don't then you don't need these images.
The recovery image is not even flashed, its executed in RAM and allowed me to access my filesystem.
The system image goes up to moving dots but doesn't finish booting.
Click to expand...
Click to collapse
If it was a blod then your method wouldn't actually work. Your post helps with with something worse than a soft brick but not the infamous proper hard brick blod.
DEVILOPS 007 said:
If it was a blod then your method wouldn't actually work. Your post helps with with something worse than a soft brick but not the infamous proper hard brick blod.
Click to expand...
Click to collapse
The whole post is not about if it works or not. IT DOES WORK to get to recovery on my device which has a BLOD :silly:
Got it?
If you don't need these images, respects others and just don't post in this thread. I'm waiting for feedback on if it works on others too.
rchtk said:
The whole post is not about if it works or not. IT DOES WORK to get to recovery on my device which has a BLOD :silly:
Got it?
If you don't need these images, respects others and just don't post in this thread. I'm waiting for feedback on if it works on others too.
Click to expand...
Click to collapse
I'm just saying that it doesn't work that often lying and the blod doesn't even let you get to recovery anyway but whatever. Believe whatever, believe what you want.
rchtk said:
My phone is 10 months old and began bootlooping a few hours ago. I've kept it in a bootloop but it never booted neither system nor recovery.
It's still under waranty but I'll keep it a few days to try a few things. I'm going on vacation next week so I'll be without phone 10 months is just unacceptable from a QA point of view from Huawei and Google. Anyway...
Up to now I get mixed results: I can boot in recovery but can't fully boot. I'll try a few others way (either kernels or parameters) later during the weekend and update this post.
Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is to limit the kernel to use less cores.
Urls:
Xtwrp-3.1.0-0-2-angler.img
Xboot-opp3.170518.006-0bc919b4.img
How to use:
Reboot into bootloader mode (hold power + volume down)
fastboot boot Ximage.img
Will boot you either in recovery or system depending on the image you use.
Feedback:
Tell me if that works out for you. Thanks.
Click to expand...
Click to collapse
Ok, so I got it booted to the TWRP 3.1.0.0 from your post but I can't see any of my files. I had TWRP 3.0.3.0 installed.
What do I do next?
I haven't tried the other image yet. I'm just excited to see what my battery percentage is so I know if I'm in the 6-9% range as mentioned in the other thread about this problem.
---------- Post added at 06:45 PM ---------- Previous post was at 06:25 PM ----------
Ok, so I just tried the opp file and it's booted up to the Google logo and stops.
outbackpaul said:
Ok, so I got it booted to the TWRP 3.1.0.0 from your post but I can't see any of my files. I had TWRP 3.0.3.0 installed.
What do I do next?
I haven't tried the other image yet. I'm just excited to see what my battery percentage is so I know if I'm in the 6-9% range as mentioned in the other thread about this problem.
Click to expand...
Click to collapse
Glad it also works for you. Well that's weird that you don't see your files under /data .
Can you try to mount /data (and maybe open shell and issue dmesg) ? Were you encrypted?
That looks similar to me. Mine was encrypted and it actually failed to decrypt it. So I formated it in the hope that it would help to boot.
---------- Post added at 06:45 PM ---------- Previous post was at 06:25 PM ----------
Click to expand...
Click to collapse
Ok, so I just tried the opp file and it's booted up to the Google logo and stops.
Click to expand...
Click to collapse
With a modified ramdisk to remove ciphering and dm-verity, mine fails right away. With the boot img I posted, the moving dots show for like 5 minutes (creating cipher metadata?) so most of the partitions are mounted but it cannot fully boot.
I did a simple check of the emmc (dding mmc to /dev/null) which is ok but I actually need to compile a pattern write and read to confirm that.
Unfortunatly, I have no USB to serial device to see eventual kernel logs.
psycho-punk said:
Also, what are the modifications done to this recovery and boot image?
Click to expand...
Click to collapse
"Boot image includes the kernel from O DP3 and recovery image the kernel from twrp 3.1.0.0. Current method is to limit the kernel to use less cores."
I have several kernels with different modifications but the original ones are actually the ones that work better. These are original kernels but called with a maxcpus parameters (isolcpu would fit better but doesn't seem to do the job).
The recovery I posted is 5 cpus IIRC, its fast enough and works from RAM but not always when flashed. Flashing a recovery when cpu is lowered to 1 always works.
Again, on MY device, might not be the same for you.
Edit: links worked with proxy
Click to expand...
Click to collapse
Weird that going through a proxy helps. Whatever.
I'll try a few others things in the next days but I'm sending the device on Thursday at the latest... I'll try to get in touch with some kernel devs. Any idea is welcome!
psycho-punk said:
Tried booting the images. Unfortunately, both of them didn't work for me.
Sent from my XT1092 using Tapatalk
Click to expand...
Click to collapse
You fastboot boot Xrecovery and it didn't boot? fastboot flash followed by rebooting into recovery might not work.
This evening, I'll post one which limits to only one core.
For the system one, it has more requirements. Not sure if there is backward compatiblity (being able to start an old ROM/vendor with a very recent kernel).
I tried so many things. Only not the oven yet
rchtk said:
Glad it also works for you. Well that's weird that you don't see your files under /data .
Can you try to mount /data (and maybe open shell and issue dmesg) ? Were you encrypted?
That looks similar to me. Mine was encrypted and it actually failed to decrypt it. So I formated it in the hope that it would help to boot.
With a modified ramdisk to remove ciphering and dm-verity, mine fails right away. With the boot img I posted, the moving dots show for like 5 minutes (creating cipher metadata?) so most of the partitions are mounted but it cannot fully boot.
I did a simple check of the emmc (dding mmc to /dev/null) which is ok but I actually need to compile a pattern write and read to confirm that.
Unfortunatly, I have no USB to serial device to see eventual kernel logs.
Click to expand...
Click to collapse
I'm pretty sure I was encrypted. I don't have the phone with me at the moment.
So, if it's encrypted am I out of luck?
When it booted to TWRP it asked for a passcode. I just hit cancel. Is that what will let me see my data?
outbackpaul said:
I'm pretty sure I was encrypted. I don't have the phone with me at the moment.
So, if it's encrypted am I out of luck?
When it booted to TWRP it asked for a passcode. I just hit cancel. Is that what will let me see my data?
Click to expand...
Click to collapse
So you're in the same boat as me (hope you had backups like me).
Twrp 3.1 should be able to decrypt /data with the correct password. I guess it first tries with default_password and if a known pattern is not detected it asks for your passcode (pin to boot by default) until it succeeds.
But for me (encrypted with pin to boot), twrp wasn't able to decrypt. In my tests once I format /data, it gets encrypted again and twrp again fails to decrypt the partition.
Can you try with pass "default_password" (without quotes) or your pin to boot if you had set one?
Also do the same after flashing the one core version I just posted and rebooting into it.
psycho-punk said:
Eagerly waiting to try the one core only recovery.
Click to expand...
Click to collapse
http://dl.free.fr/oIkytaKDF
outbackpaul said:
I'm pretty sure I was encrypted. I don't have the phone with me at the moment.
So, if it's encrypted am I out of luck?
When it booted to TWRP it asked for a passcode. I just hit cancel. Is that what will let me see my data?
Click to expand...
Click to collapse
You should also try to *flash* the one core version and see if you're able to decrypt your data with it.
rchtk said:
So you're in the same boat as me (hope you had backups like me).
Twrp 3.1 should be able to decrypt /data with the correct password. I guess it first tries with default_password and if a known pattern is not detected it asks for your passcode (pin to boot by default) until it succeeds.
But for me (encrypted with pin to boot), twrp wasn't able to decrypt. In my tests once I format /data, it gets encrypted again and twrp again fails to decrypt the partition.
Can you try with pass "default_password" (without quotes) or your pin to boot if you had set one?
Also do the same after flashing the one core version I just posted and rebooting into it.
Click to expand...
Click to collapse
I don't even remember putting in a pin but I've tried every one that I remember ever using.
psycho-punk said:
One core version didn't work either. Guess I'm out of options.
Sent from my XT1092 using Tapatalk
Click to expand...
Click to collapse
It would be interesting to start from the same configuration by using the O DP3 factory image script flash-all.sh (removing -w if you want to keep your data).
Progress:
The fact that twrp can't decrypt data with the correct password is not understood. I'm getting a KM_ERROR_KEY_NOT_YET_VALID error message. Which is rather weird.
KM_TAG_ACTIVE_DATETIME requires comparison with a trusted UTC time source. If the current date and time is prior to the tag value, the method must return KM_ERROR_KEY_NOT_YET_VALID.
So I've formated /data, disabled encryption and verify and twrp sees my /data which is populated during system boot.
Regarding boot img, I've tried several things but I still fail to get past the jumping dots. It could be a consequence of the twrp problem about communication error with the keystore which has nothing to do with big cluster disabling (so there may be a general HW failure). I've tried playing a bit with big cluster settings but my attempts fail. Still a lot of things to try but I won't have much time in the next days.
Nexus 6p bootlooping just
Tried both did not work
command used
Fastboot flash boot Xboot-opp3.170518.006-0bc919b4.img
Fastboot flash recovery Xtwrp-3.1.0-0-angler.img
and
Fastboot boot Xtwrp-3.1.0-0-angler.img
not working
RIP
Game is over for me: I've let the phone charge at home and when trying to power it back, I just get a red blinking led. I always managed to power it back but this time not.
Which brings me to the conclusion that it looks power related. Battery, soldering, IC, motherboard (components are more prone to fail stop failures).
In the end, I've mostly changed kernel stuffs (and discovered a few kernel inconsistencies btw) but didn't have time to try a lot of things in userland nor investigate on the decryption failure.
My goal was just to get users to get back their data before throwing/sending back the brick.
So I'd suggest users to decrypt their /data before BLOD happens.
A bit frustrating but was fun anyway. Thanks to @Dees_Troy for the chat on IRC