Related
Forgive if there are similar threads about this topic.
I suffered from scrolling cwm so i tried this fix: http://forum.xda-developers.com/showpost.php?p=27830023&postcount=41
It worked excellent but when i lock my screen and unlock it again it starts flickering like shown in this video: http://youtu.be/P6fMxjFdpJE
I have tried to do factory resets both from recovery and flash an original firmware. Nothing works.
Is it possible to get this fixed or am i screwed?
Hi!
I've the same trouble like you!
Try this http://forum.xda-developers.com/showthread.php?t=1680738
For me it works well both the CWM recovery that hc 3.2 (no more flickering!)
brusarp said:
Hi!
I've the same trouble like you!
Try this http://forum.xda-developers.com/showthread.php?t=1680738
For me it works well both the CWM recovery that hc 3.2 (no more flickering!)
Click to expand...
Click to collapse
I just wanted to say the same. Flash the kernel from pershoot website, it should fix it.
brusarp said:
Hi!
I've the same trouble like you!
Try this http://forum.xda-developers.com/showthread.php?t=1680738
For me it works well both the CWM recovery that hc 3.2 (no more flickering!)
Click to expand...
Click to collapse
isimobile said:
I just wanted to say the same. Flash the kernel from pershoot website, it should fix it.
Click to expand...
Click to collapse
Thank you very much. I will try this when i get home from work.
It doesn´t work for me.
But I dont use 3G anyway so can I just go with P7510 firmware which works?
nicktaken said:
It doesn´t work for me.
But I dont use 3G anyway so can I just go with P7510 firmware which works?
Click to expand...
Click to collapse
Oh... i don't know that... mine is P7500... and works well both CWM and HC3.2 (with 3G and wifi connection)
brusarp said:
Oh... i don't know that... mine is P7500... and works well both CWM and HC3.2 (with 3G and wifi connection)
Click to expand...
Click to collapse
Alright I got it to work! I didn´t get it that I should flash the kernel in cwm so I flashed it in Samsungs recovery
nicktaken said:
Alright I got it to work! I didn´t get it that I should flash the kernel in cwm so I flashed it in Samsungs recovery
Click to expand...
Click to collapse
:highfive: :good:
brusarp said:
Hi!
I've the same trouble like you!
Try this http://forum.xda-developers.com/showthread.php?t=1680738
For me it works well both the CWM recovery that hc 3.2 (no more flickering!)
Click to expand...
Click to collapse
Got the same issue today after installing Task's ROM. The fix worked for me.. Thanks man.. :good:
nicktaken said:
Forgive if there are similar threads about this topic.
I suffered from scrolling cwm so i tried this fix: http://forum.xda-developers.com/showpost.php?p=27830023&postcount=41
It worked excellent but when i lock my screen and unlock it again it starts flickering like shown in this video: http://youtu.be/P6fMxjFdpJE
I have tried to do factory resets both from recovery and flash an original firmware. Nothing works.
Is it possible to get this fixed or am i screwed?
Click to expand...
Click to collapse
When you tried the fix noted above, I assume the screen didn't roll when you rebooted then into CWM recovery. At that point did you flash a ROM and THEN reboot to find the flicker after locking the screen, or did you do a reboot back into the same stock HC after flashing the bootloader and experience the problem?
I'm contemplating flashing this same bootloader because I have a rolling CWM5.5.0.4 right now and I want to stabilize it - but just so that I can root...not thinking about a ROM just yet...
Just to inform you all, i also had to flash a different bootloader after installing cm9 on my p7511, wich is in fact a 7510. For the records, pershoot made the new bootloader for exactly that issue, not backwards. But seems to work also.
What i deal now with, is that after flashing the uk ics for p7510 to my tab, the stock recovery doesn't recognize my sdcard. Can't mount sdcard...
Could be that a repartitioning with pit file will be necessary afterwards for us all.
Edit: thanks to the wise help of msedek, i know by now that my hind was totaly wrong. My mentioned point has to do with the Changes within stock recovery of ics, which have been made to prevent changes from there.
Getting more confident..
OK so it is sounding like this is definitely better. One more question:
I'm following the stickied root guide in General and that method uses CWM 4.0.0.4...I had reflashed that version. If I want to flash this boot loader should I flash 5.5.0.4 first? Or does it matter if I'm just trying to root right now?
EDIT: Flashed the bootloader which straightened out the recovery!! Successfully rooted after that. Downloaded root apps (ROM manager/Titanium/etc). Then turned off my screen - FLICKER CITY!
http://forum.xda-developers.com/showthread.php?t=1680738 <<< THIS fixed it. Load this kernel into the root of your tablet and flash it with CWM. Seems to have done the trick nicely and I'm exploring my newly rooted tab! My wife no longer wants to kill me either.
brusarp said:
Hi!
I've the same trouble like you!
Try this http://forum.xda-developers.com/showthread.php?t=1680738
For me it works well both the CWM recovery that hc 3.2 (no more flickering!)
Click to expand...
Click to collapse
This method don't work with new ICS firmware. I need a new kernel to work with new ICS firmware . I like the new firmware but i stuck with flickerscreen issue. Can sum 1 help ? Thanks.
I have the same Problem here.
Nothing is working for me, i have tried 2 diferent kernels and still flickering screen after tourning the screen off and on.
Please can anyone help me?
KeyF said:
I have the same Problem here.
Nothing is working for me, i have tried 2 diferent kernels and still flickering screen after tourning the screen off and on.
Please can anyone help me?
Click to expand...
Click to collapse
What ROM or firmware are you running? What exactly have you done with the device up to this point? Are you 3G or WiFi? Need more detail...
Flicker screen after screen lock\timeout
djmatt604 said:
What ROM or firmware are you running? What exactly have you done with the device up to this point? Are you 3G or WiFi? Need more detail...
Click to expand...
Click to collapse
I have the same problem on my P7500 3G and the minute i load the bootloader to fix CWM recovery rolling i get the screen flickering after lock screen.
Rom: ICS 4.0.4
Build Number: IMM76D.XXLQ8
BaseBand7500XXlQ8
Kernel: 3.1.10
Still stuck.
Hi guys,
Gtab 10.1 Wifi here. Fix didn't worked, somehow...
After installing official ics from Samsung and rooted, i had the same insane flicker issue. I followed this thread - http://forum.xda-developers.com/showthread.php?t=1680738 - , flashed new kernel, and now i cant pass Samsung Galaxy Tab logo for some reason, not even past half an hour.
Im in a dead end, even tried installing back CM9 but it also wont pass the splashing blue screen.
Any ideas?
cheers!
EDIT : After some reboots, finally managed to boot into ICS (CM9) but now i was pushed back to the step 1, where I don't have a working camera, but I have root access and non official ICS from Cyanogen. I am afraid re-doing all my work and get stuck again in the scrambled screen after it updates the kernel..
I'm I missing something, guys?
Hi there!
Are you still having problems?does this guide here work for you?:
http://forum.xda-developers.com/showthread.php?t=1555984
I've found something,the kernel flash package changes our devices' WiFi driver,that's why it doesn't work.
sorry for not giving a fix until tomorrow,it's sleep time here,I know my excuse will be accepted because you all care for basic human needs...
But please inform me if that guide(Pershoot's) has fixed your problem,thanks for that
brusarp said:
Hi!
I've the same trouble like you!
Try this http://forum.xda-developers.com/showthread.php?t=1680738
For me it works well both the CWM recovery that hc 3.2 (no more flickering!)
Click to expand...
Click to collapse
No it does not work for me.
I have a GT-P7500 with ICS with Build # IMM76D.XWLP6
Please direct me to the correct forum.
thanX
reXbeer said:
No it does not work for me.
I have a GT-P7500 with ICS with Build # IMM76D.XWLP6
Please direct me to the correct forum.
thanX
Click to expand...
Click to collapse
Hey guys i solve my problem today i desided to solve it anyway and now i am free from this **** ....
i just go to http://droidbasement.com/galaxy/roms/cm10/p4/ and download
bootloader.tar.md5
latest recovery.tar.md5
cm-10-20121112-EXPERIMENTAL-p4.zip
but before start anything first i format my tab memory then restart in download mode install bootloader.tar.md5 and recovery.tar.md5 ... volla ... reboot in recovery mode volla thats it all is now working perfect .... then i install cm-10-20121112-EXPERIMENTAL-p4.zip now my tab is free on madness ...
must try but first fully clean your tab ...
iff its really work then click on thanks button ...
Okay so I received an Asus Transformer Prime tf201 yesterday. This morning I was able to unlock it, root it, and then I wanted to install the latest nightly of CM10 (24th). After I saw that it was indeed rooted I booted into twrp and in Wipe I did Factory Reset, System, Internal Storage (wanted to get rid of the pictures, etc. from previous owner). I had CM10 latest nightly and gapps both on my External SD Card so I knew I wasn't removing those.
Anyway after clicking on Install and then Using external SD I selected the zip of CM10 and swiped to confirm flash. It does well for about 2 or 3 minutes (the blue bar even shows progress) and then it comes up with the message E:Unable to mount '/staging'.
Please please tell me I did not mess up my Prime when I just got it???!!! Anyone that can help please help as soon as possible as I am really wanting to play with this after all the fantastic reviews I have heard. You would have my eternal gratitude and if it is not wrong to do this I will even donate via PayPal to the person that can help me "fix" my Prime.
Please KNOW I have been looking for answers to this for HOURS today and still haven't found anything to help me. I am really hoping some genius on XDA can help me.
alias4ever said:
Okay so I received an Asus Transformer Prime tf201 yesterday. This morning I was able to unlock it, root it, and then I wanted to install the latest nightly of CM10 (24th). After I saw that it was indeed rooted I booted into twrp and in Wipe I did Factory Reset, System, Internal Storage (wanted to get rid of the pictures, etc. from previous owner). I had CM10 latest nightly and gapps both on my External SD Card so I knew I wasn't removing those.
Anyway after clicking on Install and then Using external SD I selected the zip of CM10 and swiped to confirm flash. It does well for about 2 or 3 minutes (the blue bar even shows progress) and then it comes up with the message E:Unable to mount '/staging'.
Please please tell me I did not mess up my Prime when I just got it???!!! Anyone that can help please help as soon as possible as I am really wanting to play with this after all the fantastic reviews I have heard. You would have my eternal gratitude and if it is not wrong to do this I will even donate via PayPal to the person that can help me "fix" my Prime.
Please KNOW I have been looking for answers to this for HOURS today and still haven't found anything to help me. I am really hoping some genius on XDA can help me.
Click to expand...
Click to collapse
Did you check in twrp under the mounts button? I don't have my prime with me atm but I know there is a mounts section either on the first screen or under advanced may be....
Gage_Hero said:
Did you check in twrp under the mounts button? I don't have my prime with me atm but I know there is a mounts section either on the first screen or under advanced may be....
Click to expand...
Click to collapse
Yeahup I tried mounting everything and then unmounting everything to try and get it to work. What should be mounted/unmounted and selected on either SD Card or Internal? THANKS!
alias4ever said:
Yeahup I tried mounting everything and then unmounting everything to try and get it to work. What should be mounted/unmounted and selected on either SD Card or Internal? THANKS!
Click to expand...
Click to collapse
Mine, the radio button for external is on, you could try the terminal under advanced button...command would be something like su then enter and then mount /staging or something like that.... you may want to check the command exactly, my terminal skills are limited...
alias4ever said:
Yeahup I tried mounting everything and then unmounting everything to try and get it to work. What should be mounted/unmounted and selected on either SD Card or Internal? THANKS!
Click to expand...
Click to collapse
Probably running TRWP 2.3.x.x, right? Some others had this same problem with the TF300 and switched back to TWRP 2.2.2.1 and their ROM flashed just fine. Might be worth a shot.
tedr108 said:
Probably running TRWP 2.3.x.x, right? Some others had this same problem with the TF300 and switched back to TWRP 2.2.2.1 and their ROM flashed just fine. Might be worth a shot.
Click to expand...
Click to collapse
Isn't 2.3 for the JB bootloader and 2.2 for ics though?
Gage_Hero said:
Isn't 2.3 for the JB bootloader and 2.2 for ics though?
Click to expand...
Click to collapse
No, there is a 2.3 for both ics and jb bootloaders ... I THINK that 2.2 was ics only (can't remember for sure). If he was loading the CM10 nightly, he should have had an ics bootloader, or it would not have run.
---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------
Gage_Hero said:
Isn't 2.3 for the JB bootloader and 2.2 for ics though?
Click to expand...
Click to collapse
You do bring up a good point, though ... if his TFP had a JB OTA, he could have the jb bootloader! Alias, you need to check these types of things out before moving forward.
tedr108 said:
No, there is a 2.3 for both ics and jb bootloaders ... I THINK that 2.2 was ics only (can't remember for sure). If he was loading the CM10 nightly, he should have had an ics bootloader, or it would not have run.
---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------
You do bring up a good point, though ... if his TFP had a JB OTA, he could have the jb bootloader! Alias, you need to check these types of things out before moving forward.
Click to expand...
Click to collapse
I had the JB OTA before starting I do know that. Would have kept it if I didn't love CM so much! So would I just install twrp 2.2 through fastboot then like I did the 2.3.1.0 that I have now? Or is there another way I can do this? Thank you BOTH for your help! It is much appreciated! :good:
alias4ever said:
I had the JB OTA before starting I do know that. Would have kept it if I didn't love CM so much! So would I just install twrp 2.2 through fastboot then like I did the 2.3.1.0 that I have now? Or is there another way I can do this? Thank you BOTH for your help! It is much appreciated! :good:
Click to expand...
Click to collapse
If you had the JB bootloader before, then you surely still have it. You would not change your bootloader by flashing a CM10 nightly ROM. The only way that I know of for you to go back to an ICS bootloader is with nvflash. If nvflash was not on your TFP when you got it, you won't be getting it anytime soon, because it cannot be installed with a JB bootloader on your TFP.
Which TWRP 2.3.1 did you load? The JB version?
The CM10 nightlies are not currently compatible with a JB bootloader, so you had no hope of running it. That may very well have caused your staging error, but I am not sure. Since you apparently have a JB bootloader, you would have to flash an appropriate ROM, like Craig Gomez' (here). But, only the JB version of TWRP 2.3.1 will work for you, as far as I know. So, I'm thinking you must have loaded the correct one.
I cannot be 100% sure that you have the JB bootloader. I hope you are sure that your TFP was updated to JB by an Asus update (OTA).
If I were you, I'd make a plan of action and post it here. Be patient and wait for a response, before moving forward. Good luck with this.
alias4ever said:
I had the JB OTA before starting I do know that. Would have kept it if I didn't love CM so much! So would I just install twrp 2.2 through fastboot then like I did the 2.3.1.0 that I have now? Or is there another way I can do this? Thank you BOTH for your help! It is much appreciated! :good:
Click to expand...
Click to collapse
the only way back to an ics bootloader it through nvflash... if you didn't do nvflash before you started with JB then you are stuck using jb roms only I think.....you could try hairy bean .....
tedr108 said:
If you had the JB bootloader before, then you surely still have it. You would not change your bootloader by flashing a CM10 nightly ROM. The only way that I know of for you to go back to an ICS bootloader is with nvflash. If nvflash was not on your TFP when you got it, you won't be getting it anytime soon, because it cannot be installed with a JB bootloader on your TFP.
Which TWRP 2.3.1 did you load? The JB version?
The CM10 nightlies are not currently compatible with a JB bootloader, so you had no hope of running it. That may very well have caused your staging error, but I am not sure. Since you apparently have a JB bootloader, you would have to flash an appropriate ROM, like Craig Gomez' (here). But, only the JB version of TWRP 2.3.1 will work for you, as far as I know. So, I'm thinking you must have loaded the correct one.
I cannot be 100% sure that you have the JB bootloader. I hope you are sure that your TFP was updated to JB by an Asus update (OTA).
If I were you, I'd make a plan of action and post it here. Be patient and wait for a response, before moving forward. Good luck with this.
Click to expand...
Click to collapse
Okay let's see if I can get this is all right. I have The JB version of TWRP 2.3.1. As for running a different ROM I tried the Unofficial one you listed and it still gives me the Unable to mount 'staging/' error. It first says it is verifying the signature then update package, then it says Updating partition details and that is when it comes to the staging error. :crying:
I am 110% positive that my TFP was updated to JB by the Asus update (OTA). Thanks again for the suggestions hopefully someone out there will suggest something.
What about doing the PRIME FULL WIPE that someone suggests here: http://forum.xda-developers.com/showthread.php?t=1670824 Then trying to install the Unofficial CM10 with the JB Bootloader? Anyone know if this would work?
alias4ever said:
Okay let's see if I can get this is all right. I have The JB version of TWRP 2.3.1. As for running a different ROM I tried the Unofficial one you listed and it still gives me the Unable to mount 'staging/' error. It first says it is verifying the signature then update package, then it says Updating partition details and that is when it comes to the staging error. :crying:
I am 110% positive that my TFP was updated to JB by the Asus update (OTA). Thanks again for the suggestions hopefully someone out there will suggest something.
What about doing the PRIME FULL WIPE that someone suggests here: http://forum.xda-developers.com/showthread.php?t=1670824 Anyone know if this would work?
Click to expand...
Click to collapse
I wouldn't try the full wipe... what I would try is the fix permissions button under advanced.... failing that... I would try fastboot install of twrp 2.3 again (instructions on the twrp OP).... it is like you don't have rights to write to the staging partition...
Read this thread... this guy was in the same boat... page 2 post 19 is where he fixed it....
http://forum.xda-developers.com/showthread.php?t=1942927&highlight=unable+to+mount+staging&page=2
@Alias -- I was really hoping the JB bootloader ROMs would do it for you.
This right here is excellent advice from Gage_Hero:
Gage_Hero said:
I wouldn't try the full wipe... what I would try is the fix permissions button under advanced.... failing that... I would try fastboot install of twrp 2.3 again (instructions on the twrp OP).... it is like you don't have rights to write to the staging partition...
Click to expand...
Click to collapse
If this does not work, I am at a loss of how to recreate the Staging partition (and perhaps others), but there is probably a way.
Gage_Hero said:
I wouldn't try the full wipe... what I would try is the fix permissions button under advanced.... failing that... I would try fastboot install of twrp 2.3 again (instructions on the twrp OP).... it is like you don't have rights to write to the staging partition...
Read this thread... this guy was in the same boat... page 2 post 19 is where he fixed it....
http://forum.xda-developers.com/showthread.php?t=1942927&highlight=unable+to+mount+staging&page=2
Click to expand...
Click to collapse
You are an ABSOLUTE GENIUS! I remember reading that post of the guy in the same boat and honestly did not think it would work for me because I kept trying to install the different ROM's but it WORKED! Thank you, thank you, THANK YOU to you and everyone else for their suggestions! @Gage, can I send you a little thank you on PayPal??? Thank you so MUCH AGAIN! I can't thank you enough...
Now do I dare flash the CM10 Unofficial with the JB Boatloader through GooManager??? :silly:
alias4ever said:
You are an ABSOLUTE GENIUS! I remember reading that post of the guy in the same boat and honestly did not think it would work for me because I kept trying to install the different ROM's but it WORKED! Thank you, thank you, THANK YOU to you and everyone else for their suggestions! @Gage, can I send you a little thank you on PayPal??? Thank you so MUCH AGAIN! I can't thank you enough...
Now do I dare flash the CM10 Unofficial with the JB Boatloader through GooManager??? :silly:
Click to expand...
Click to collapse
Glad to get you up and running again just do yourself a favor before you try cm10.... make a backup... or 2 I never used cm on my tab but did it on my phone.... when I restored... I had to do it twice... not sure if that is the case with the prime or not ... but if it is a JB bootloader then you should be okay... I like flashing through twrp though .. never did a rom through goo... but I am sure it works...
I need a little more help now. I went to boot into TWRP last night and I just got the dead Andy. Does that mean that putting this stock JB back on my TFP I have lost my TWRP recovery?
My TFP is rooted though as I have SU in my app drawer and I installed Titanium Backup just fine. I just wanted to make a couple of backups of my TFP (one to save on my PC and one to save on my TFP's External SD. So my question is can I reinstall my TWRP through Fastboot like I did before even with it rooted? First time I did it I followed these instructions:
http://www.youtube.com/watch?v=-pW05Jf87dg&feature=plcp
But upon further reading it states that people have had problems installing JB ROMs with using the 2.3 or 2.3.1 version so should I install the 2.2 version? Please someone help me yet again possibly??? THANKS!
alias4ever said:
I need a little more help now. I went to boot into TWRP last night and I just got the dead Andy. Does that mean that putting this stock JB back on my TFP I have lost my TWRP recovery?
My TFP is rooted though as I have SU in my app drawer and I installed Titanium Backup just fine. I just wanted to make a couple of backups of my TFP (one to save on my PC and one to save on my TFP's External SD. So my question is can I reinstall my TWRP through Fastboot like I did before even with it rooted? First time I did it I followed these instructions:
http://www.youtube.com/watch?v=-pW05Jf87dg&feature=plcp
But upon further reading it states that people have had problems installing JB ROMs with using the 2.3 or 2.3.1 version so should I install the 2.2 version? Please someone help me yet again possibly??? THANKS!
Click to expand...
Click to collapse
I think people have had issues installing 2.2 on the JB bootloader I would fastboot install 2.3.1 there is no reason it shouldn't work..... I think there is some disconnect between twrp and some of the jb roms as some devs are including twrp in their install like Mr.Wookie over at team wookie.....
Gage_Hero said:
I think people have had issues installing 2.2 on the JB bootloader I would fastboot install 2.3.1 there is no reason it shouldn't work..... I think there is some disconnect between twrp and some of the jb roms as some devs are including twrp in their install like Mr.Wookie over at team wookie.....
Click to expand...
Click to collapse
Okay so I went ahead and have redone TWRP 2.3.1 via Fastboot. I then did a backup of my ROM twice onto my External SD card. After that I did a a Factory Reset through TWRP of course and then installed the Unofficial CM10 with JB Bootloader. I still got the E:can not mount '/staging' but I went ahead and installed the Gapps that was listed on the thread as well and then wiped davlik cache and regular cache. Rebooted and I am VERY HAPPY to say it FINALLY worked this time!
I was ecstatic to see that CyanogenMod symbol come up. I made sure to wait 10 minutes to let the ROM settle before doing anything and it looks very nice!
I am confused as to why it worked the second time or even worked with the staging error as well when it didn't last time. Maybe because I didn't do the wipe Internal in TWRP? Who knows all I know is my Asus is working wonderfully and I am SO HAPPY to have it back! Thank you again everyone for all your help, I LOVE THIS FORUM! :laugh: :good:
alias4ever said:
Okay so I went ahead and have redone TWRP 2.3.1 via Fastboot. I then did a backup of my ROM twice onto my External SD card. After that I did a a Factory Reset through TWRP of course and then installed the Unofficial CM10 with JB Bootloader. I still got the E:can not mount '/staging' but I went ahead and installed the Gapps that was listed on the thread as well and then wiped davlik cache and regular cache. Rebooted and I am VERY HAPPY to say it FINALLY worked this time!
I was ecstatic to see that CyanogenMod symbol come up. I made sure to wait 10 minutes to let the ROM settle before doing anything and it looks very nice!
I am confused as to why it worked the second time or even worked with the staging error as well when it didn't last time. Maybe because I didn't do the wipe Internal in TWRP? Who knows all I know is my Asus is working wonderfully and I am SO HAPPY to have it back! Thank you again everyone for all your help, I LOVE THIS FORUM! :laugh: :good:
Click to expand...
Click to collapse
Good to hear.... not sure if your aware or not but with a decent backup ( I do one everytime I think I am going to try something foolish) even if you do a wipe, as long as you can reach twrp you can restore the prime to it's state before you started messing with it....
Hi,
I won't give you the long story so here's what happened:
- TouchscreenDigitizer & LCD broke
- Replaced both
- Got a different rev of the Digitizer, result: X-Axis is inverted
- Someone (darksawa) built a patch for this by editing the touchscreen driver but you need nvflash enabled to replace the kernel image the easy way
- Was on JB Stock without root/unlock until now so I'm not able to enable nvflash
- There is a way to get it done anyway: Get the edited kernel image into another rom and install it via TWRP
- Tried to extract the stock rom (unpack blob files etc..) and replaced the kernel image - then pack all together again but wasn't working (flashing procedure abrupted, no brick)
Could someone of you do me and some other guys a big favour by replacing the original kernel image of the stock rom WW-10.4.2.15 with this kernel image?
Thank you!!!
mechadream said:
Hi,
I won't give you the long story so here's what happened:
- TouchscreenDigitizer & LCD broke
- Replaced both
- Got a different rev of the Digitizer, result: X-Axis is inverted
- Someone (darksawa) built a patch for this by editing the touchscreen driver but you need nvflash enabled to replace the kernel image the easy way
- Was on JB Stock without root/unlock until now so I'm not able to enable nvflash
- There is a way to get it done anyway: Get the edited kernel image into another rom and install it via TWRP
- Tried to extract the stock rom (unpack blob files etc..) and replaced the kernel image - then pack all together again but wasn't working (flashing procedure abrupted, no brick)
Could someone of you do me and some other guys a big favour by replacing the original kernel image of the stock rom WW-10.4.2.15 with this kernel image?
Thank you!!!
Click to expand...
Click to collapse
No I can't but I can go one better for you
I have converted it to a blob file and put it into an installable zip. Just flash this in twrp and your good to go.
This is for Jellybean.
flumpster said:
No I can't but I can go one better for you
I have converted it to a blob file and put it into an installable zip. Just flash this in twrp and your good to go.
This is for Jellybean.
Click to expand...
Click to collapse
Thank you very much for you help but I got the following problem:
I flashed the file via TWRP and now I'm stuck at the ASUS Boot-Logo with the tegra logo on the bottom right.
mechadream said:
Thank you very much for you help but I got the following problem:
I flashed the file via TWRP and now I'm stuck at the ASUS Boot-Logo with the tegra logo on the bottom right.
Click to expand...
Click to collapse
I tested the kernel myself before uploading it for you mate.. It worked fine. Everything was reversed for me when I booted back into the rom.
You could try doing a factory reset and a cache and dalvik wipe to see if that is your problem.
I was running hairybean 1.3 on jellybean when I tested it.
What rom are you running ?
flumpster said:
I tested the kernel myself before uploading it for you mate.. It worked fine. Everything was reversed for me when I booted back into the rom.
You could try doing a factory reset and a cache and dalvik wipe to see if that is your problem.
I was running hairybean 1.3 on jellybean when I tested it.
What rom are you running ?
Click to expand...
Click to collapse
I am on Stock. Installed Stock from Asus website, installed TWRP via fastboot and then flashed your file.
EDIT: factory reset, cache and dalvik wipe does not help, you suggest I install hairybean too?
mechadream said:
I am on Stock. Installed Stock from Asus website, installed TWRP via fastboot and then flashed your file.
EDIT: factory reset, cache and dalvik wipe does not help, you suggest I install hairybean too?
Click to expand...
Click to collapse
After you flashed my zip did you see a blue progress bar go along after you restarted the prime. If you did then the kernel definately flashed.
You can also try holding down the power button and volume down button until you get to the place where there are 4 icons and then going over to the wipe data icon and selecting that. That should factory reset your machine.
If that doesn't work let me know.
flumpster said:
After you flashed my zip did you see a blue progress bar go along after you restarted the prime. If you did then the kernel definately flashed.
You can also try holding down the power button and volume down button until you get to the place where there are 4 icons and then going over to the wipe data icon and selecting that. That should factory reset your machine.
If that doesn't work let me know.
Click to expand...
Click to collapse
Got that blue progress bar the first time after I flashed your file, then it went away and thats all.
Just did the wipe the way you told me, no change, still stuck @ splash screen. I think I have to install another complete rom to get over the splash screen again.
mechadream said:
Got that blue progress bar the first time after I flashed your file, then it went away and thats all.
Just did the wipe the way you told me, no change, still stuck @ splash screen. I think I have to install another complete rom to get over the splash screen again.
Click to expand...
Click to collapse
Well you're definitely not bricked so don't panic.
I think the next step would be to install a rom like you say. Try installing Hairybean 1.3 and follow all the steps in the original post. If you are still stuck after that I think the next step will be to run a full wipe script on your prime and then install a rom.
Try the rom first and let me know how you get on. We will get this sorted soon enough
Also before you install the rom, factory reset, wipe cache, dalvik and system then install.
flumpster said:
Well you're definitely not bricked so don't panic.
I think the next step would be to install a rom like you say. Try installing Hairybean 1.3 and follow all the steps in the original post. If you are still stuck after that I think the next step will be to run a full wipe script on your prime and then install a rom.
Try the rom first and let me know how you get on. We will get this sorted soon enough
Also before you install the rom, factory reset, wipe cache, dalvik and system then install.
Click to expand...
Click to collapse
Installed like you said and it's WORKING!!!
Thank you very much, after all these frustrating months it's working now, thank you thank you thank you!!
And thanks to sawa of course :good:
mechadream said:
Installed like you said and it's WORKING!!!
Thank you very much, after all these frustrating months it's working now, thank you thank you thank you!!
And thanks to sawa of course :good:
Click to expand...
Click to collapse
Glad you got it all fixed mate. I have no idea what went wrong for you as it worked first time for me but as long as it's all done now
flumpster said:
Glad you got it all fixed mate. I have no idea what went wrong for you as it worked first time for me but as long as it's all done now
Click to expand...
Click to collapse
Can I use this with Hairy Bean 1.4 too?
mechadream said:
Can I use this with Hairy Bean 1.4 too?
Click to expand...
Click to collapse
Yea, it should be okay on any stock based jellybean rom.
same problem
I have the same problem as the original treath.
I am not rooted, not unlocked under jelly bean.
Beginner question but is it also possible to install without root. how i understood TWRP needs root.
you can help me soo much ...
oremy said:
I have the same problem as the original treath.
I am not rooted, not unlocked under jelly bean.
Beginner question but is it also possible to install without root. how i understood TWRP needs root.
you can help me soo much ...
Click to expand...
Click to collapse
You need to be unlocked to install TWRP. Once installed you can flash the zip. Root is not required to install TWRP.
Thank you all!! i managed ... fully operational prime again ...
i was getting used to the mirrored clicking
Stuck at the ASUS Boot-Logo. FW US
My problem started two month ago when the repair assistance sent me back my tf201 with reverse axis. I broke the glass and they this but the didn't do the reversed axis. They wasted my time and money. I realy need help.
I am on Stock US-10.4.2.15 unlocked bootloader with TWRP and I have same problem that "!mechadream" had. I'm stuck at the ASUS Boot-Logo.
Maybe I shouldn't flash this WW(I don't know if this make some difference honestly) but I had some hope that finally solve my problem and fix it.
Now I am stuck. What should I do now? I can I do? Can you help me please? Thank you for your help.
fabianogalaxy said:
My problem started two month ago when the repair assistance sent me back my tf201 with reverse axis. I broke the glass and they this but the didn't do the reversed axis. They wasted my time and money. I realy need help.
I am on Stock US-10.4.2.15 unlocked bootloader with TWRP and I have same problem that "!mechadream" had. I'm stuck at the ASUS Boot-Logo.
Maybe I shouldn't flash this WW(I don't know if this make some difference honestly) but I had some hope that finally solve my problem and fix it.
Now I am stuck. What should I do now? I can I do? Can you help me please? Thank you for your help.
Click to expand...
Click to collapse
Can you tell me where you can get to please? can you get into TWRP? can you get to fastboot?
TWRP
flumpster said:
Can you tell me where you can get to please? can you get into TWRP? can you get to fastboot?
Click to expand...
Click to collapse
I am not sure about fastboot BUT the TWRP is working well. I can get into TWRP.
Thanks a lot.
fabianogalaxy said:
I am not sure about fastboot BUT the TWRP is working well. I can get into TWRP.
Thanks a lot.
Click to expand...
Click to collapse
Can you try installing hairybean 1.51 following all the instructions to install it including doing the wipes it tells you to.
TF201
flumpster said:
Can you try installing hairybean 1.51 following all the instructions to install it including doing the wipes it tells you to.
Click to expand...
Click to collapse
Thank you. I did what you asked me. THIS IS PERFECT!! Glad to have people like you in the world. Your help has saved my TF201. thank you :laugh::good:
Any suggestions? I've done everything, as it's said in the instruction. I only had a problem with Formating Data - the process always finished with failure, but I skipped it.
[Update]
After doing a reset I managed to stuck on androwood Prime logo.
maxonick said:
Any suggestions? I've done everything, as it's said in the instruction. I only had a problem with Formating Data - the process always finished with failure, but I skipped it.
[Update]
After doing a reset I managed to stuck on androwood Prime logo.
Click to expand...
Click to collapse
You have a problem if you cannot format data. You cannot simply miss steps because they don't work.
Try getting the downgrade zip that will take you back to the 4.1.1 bootloader and compatible twrp.
Then try doing all the wipes suggested before and try installing hairybean 1.51
If that all works try the upgrade process again.
quo nksgide
flumpster said:
You have a problem if you cannot format data. You cannot simply miss steps because they don't work.
Try getting the downgrade zip that will take you back to the 4.1.1 bootloader and compatible twrp.
Then try doing all the wipes suggested before and try installing hairybean 1.51
If that all works try the upgrade process again.
Click to expand...
Click to collapse
Is there a way to fix without downgrading?
maxonick said:
Is there a way to fix without downgrading?
Click to expand...
Click to collapse
It is not working. What is the problem with trying the downgrade zip to see if it fixes it?
I wiped the internal storage, now it seems to be loading.
[Update] Stuck again.
flumpster said:
It is not working. What is the problem with trying the downgrade zip to see if it fixes it?
Click to expand...
Click to collapse
Tried your method, flashed downgrade.zip, still stucks on Formating data. Same error.
maxonick said:
Tried your method, flashed downgrade.zip, still stucks on Formating data. Same error.
Click to expand...
Click to collapse
I have never seen this. Can you look in mounts and see what is ticked on and what can and can't be ticked on.
flumpster said:
I have never seen this. Can you look in mounts and see what is ticked on and what can and can't be ticked on.
Click to expand...
Click to collapse
Managed to install HearyBean 1.51, by the way, seems, successfully. I'll post here, if I'll have any success with upgrading to HearyBean 2.2
flumpster said:
I have never seen this. Can you look in mounts and see what is ticked on and what can and can't be ticked on.
Click to expand...
Click to collapse
Think found it! There was no blue loading line after flashing, cause I powered off instead of rebooting, now I'll try to install.
maxonick said:
Think found it! There was no blue loading line after flashing, cause I powered off instead of rebooting, now I'll try to install.
Click to expand...
Click to collapse
Stuck on the Asus logo.
Thank you for your help! Your ROM is GREAT!!!
Hello everyone, let me just go ahead and say that I'm a total noob in the android customization thing but I somehow manage to install Lineage OS on my L03 and at the time I thought it was done and I didn't messed anything up but somehow that backfire on me.
So right now my HAM 2 is on a boot-loop, it kept staying the Lineage OS loading screen and once it was done and show the device setup screen for like 3 seconds it goes black and load again.
I've tried everything to fix it, from reinstalling an older version of Lineage, install CM13, wipe all data cache and dalvik ( and yes I have install gapps everytime I install any custom ROM, and finally after looks around the web I thought It might be the power button that making it acts weird but when after cleans it with rubbing alcohol (70%) It's still happening.
Now I have 2 options, first is to downgrade the firmware ( I'm not sure if it safe and how to do it) and seconds is to downgrade or delete TWRP ( newest version on HAM2).
Please, if anyone knows how to fix this. Help me. I got this device from amazon and it'll be a hassle trying to claim warranty on it since I have unlock it's boot-loader and install a custom ROM.
Thanks in advance.
Im not trying to be an asshole but does no one know how I can fix this?.
Bl4ckAir said:
Im not trying to be an asshole but does no one know how I can fix this?.
Click to expand...
Click to collapse
Are you using MDMower's latest version of TWRP for the Mate 2 (3.1.N0-0) ?
divhandyman said:
Are you using MDMower's latest version of TWRP for the Mate 2 (3.1.N0-0) ?
Click to expand...
Click to collapse
I'm using the offical Teamwin TWRP 3.1.1.0 for mt2l03.
Bl4ckAir said:
I'm using the offical Teamwin TWRP 3.1.1.0 for mt2l03.
Click to expand...
Click to collapse
That one never works for me. Flash this version of TWRP and flash the latest version of Lineage OS 20170903.
https://www.androidfilehost.com/?a=show&w=files&flid=40887
divhandyman said:
That one never works for me. Flash this version of TWRP and flash the latest version of Lineage OS 20170903.
https://www.androidfilehost.com/?a=show&w=files&flid=40887
Click to expand...
Click to collapse
Could you elaborate on how to do that? Can I flash it in the old TWRP or ADB on desktop? Thanks.
Bl4ckAir said:
Could you elaborate on how to do that? Can I flash it in the old TWRP or ADB on desktop? Thanks.
Click to expand...
Click to collapse
Yes use ADB.
https://www.youtube.com/watch?v=OwY-K6-pmJU&feature=youtu.be
Bl4ckAir said:
Please, if anyone knows how to fix this.
Click to expand...
Click to collapse
Well, it seems that you missed all of the fun & games last week in the following thread:
https://forum.xda-developers.com/ascend-mate2/help/candy7-cm13-rom-restarting-loop-issue-t3661885
"divhandyman" gets right to the point by correctly recommending MDMower's repo @ AndroidFileHost. My discussions on the topic are slightly more wordy (we all have our faults, yes?), but MDMower's TWRP & LineageOS 09/03 (or newer) is all that you need because the boot loop fix is baked-in.
As a side note, my original instructions assumed a degree of basic knowledge and did not include guides to installing TWRP, making backups, moving files, using ADB/fastboot, etc... These tools and procedures are well documented, ad nauseam, elsewhere.
hola
have you managed to solve it?
I have the same problem!!!
please help
Douglas_27 said:
have you managed to solve it?
I have the same problem!!!
please help
Click to expand...
Click to collapse
Hi, Douglas I have managed to solved it. Please tell me the step you have taken and I'll maybe able to help you.
Does it work for L01 the latest TWRP
EndlessFall said:
Well, it seems that you missed all of the fun & games last week in the following thread:
https://forum.xda-developers.com/ascend-mate2/help/candy7-cm13-rom-restarting-loop-issue-t3661885
"divhandyman" gets right to the point by correctly recommending MDMower's repo @ AndroidFileHost. My discussions on the topic are slightly more wordy (we all have our faults, yes?), but MDMower's TWRP & LineageOS 09/03 (or newer) is all that you need because the boot loop fix is baked-in.
As a side note, my original instructions assumed a degree of basic knowledge and did not include guides to installing TWRP, making backups, moving files, using ADB/fastboot, etc... These tools and procedures are well documented, ad nauseam, elsewhere.
Click to expand...
Click to collapse
I tried the latest TWRP from MDMower but got stuck in a boot loop after I flashed it and went to turn off the phone to go into recovery mode.
i mistakingly delete a file on my huawei mt2-l02 and since then when i power on it will stuck on startup anyone with solution