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:
Related
So, i had my gtab working fine then i tried to go to BL 1.2, had a rom running for a while then decided i wanted to go back to a 1.1 rom, I nvflashed to 1.1 stock image and now my tablet wont boot on any rom that isnt NVflashed, regardless of if i use CWM or stock recovery, what am i doing wrong? It only runs stock Viewsonic roms
What rom were you trying to flash that you could only use on 1.1 that there isn't a port running for 1.2.?
Let me guess. You never wiped out your data before you flash a new rom.
This is a common mistake made by beginners. Is this the case?
goodintentions said:
Let me guess. You never wiped out your data before you flash a new rom.
This is a common mistake made by beginners. Is this the case?
Click to expand...
Click to collapse
No, this is not the case, i am aware that NVflashing changes partition sizes, is it possible that customs roms are larger than Viewsonics rom and there isnt sufficient space to load a custom rom?
Mantara said:
What rom were you trying to flash that you could only use on 1.1 that there isn't a port running for 1.2.?
Click to expand...
Click to collapse
I was running BOS on 1.2 but i was having isues where if the tablet was powered off after initial boot it would not booot again so i wanted to run the 1.1 honeycomb
Have you used cwm to repartition and then load a rom?
Mantara said:
Have you used cwm to repartition and then load a rom?
Click to expand...
Click to collapse
Yes, but from what i know you can only partition the internal SD from CWM
Did you update using ota from stock brfore trying to flash another rom?
How about this. What version of nvflash are you using? I don't just mean 1.1 or 1.2. I'm talking about the long string of number in the nvflash zip file.
There are some nvflash versions floating out there that are bad.
Try this. Go to my website at
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
Use the code red procedure. Don't use anything you already have. Download everything from my website. Follow the procedure I outlined. See if this changes anything.
goodintentions said:
How about this. What version of nvflash are you using? I don't just mean 1.1 or 1.2. I'm talking about the long string of number in the nvflash zip file.
There are some nvflash versions floating out there that are bad.
Try this. Go to my website at
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
Use the code red procedure. Don't use anything you already have. Download everything from my website. Follow the procedure I outlined. See if this changes anything.
Click to expand...
Click to collapse
my NVflash is not the same extention but the 1.1 file has the same extention as yours, ill try to flash yours anyways.
Mantara said:
Did you update using ota from stock brfore trying to flash another rom?
Click to expand...
Click to collapse
Ive tried ota and NVflash to 1.1 directly neither work
http://forum.xda-developers.com/showpost.php?p=13474033&postcount=114
Was written for linux you might need to adjust the nvflash commands for windows.
Thanks all of you, I got it to run BOS on 1.2 using goodintentions' NVflash, idk what happened but it appears to be working weirdly though, it wont boot a second time without a factory data reset
whodatxevg said:
Thanks all of you, I got it to run BOS on 1.2 using goodintentions' NVflash, idk what happened but it appears to be working weirdly though, it wont boot without a factory data reset
Click to expand...
Click to collapse
Didn't I tell you to use code red on my start here page? Part of the instructions in code red is to wipe data/factory reset.
You didn't really read my code red did you?
goodintentions said:
Didn't I tell you to use code red on my start here page? Part of the instructions in code red is to wipe data/factory reset.
You didn't really read my code red did you?
Click to expand...
Click to collapse
It wont boot without a data reset AFTER the initial boot. I dont think its normal to have to do a data reset after a rom is already installed but that seems to be a rom issue
Yep. Rom issue. Bos needs to be factory reset after flash. Its odd but what needs to happen to boot initially.
Glad to see you got her up and running
Mantara said:
Yep. Rom issue. Bos needs to be factory reset after flash. Its odd but what needs to happen to boot initially.
Click to expand...
Click to collapse
Oh well, thats why its not a final build.
Thanks again guys.
I suggest that all HC roms have a boot splash screen that simply states "This is an Alpha build, please on't expect everything to work like you want it to"
People keep having these delusions that the HC roms will work perfectly...
whodatxevg said:
It wont boot without a data reset AFTER the initial boot. I dont think its normal to have to do a data reset after a rom is already installed but that seems to be a rom issue
Click to expand...
Click to collapse
No it's not a rom issue.
As I explained on my website, the problem is that nvflash DOES NOT wipe out your data. When you nvflash a new stock rom, the data from the previous rom is still there. Some are not compatible with the stock rom, so the left over data cause an interruption in the normal boot process. Sometimes, it bootloops. Sometimes, you are kicked into permanent apx mode.
That's why in my code red procedure I told you to wipe data/factory reset RIGHT AFTER you nvflash.
There's a purpose to the way I ordered my instructions.
Better read the instructions better next time. Could have saved you hours of frustration.
And yes, it is normal to wipe data before you flash a new rom. Since nvflash doesn't wipe data, you have to wipe data manually after you nvflash. It's the same as wiping data before you flash the stock rom.
There have been cases with bos where full wipes were done (as far as were stated in the posts but we know no one ever lies right?) and it would bootloop untilled full wipes were done again. Who knows.
Personally I wipe and repartition every time I flash a new rom. If its an update I leave it, if its a new rom I start from a clean slate. I use titanium backup almost daily and have copies of my recovery backup on my PC weekly. Its slightly time consuming but unborking takes a hell of a lot longer than being extra cautious when flashing
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 ...
Hey guys have to forgive me very tired spent last 11 hours trying to get this working again but im stuck now and im at my wits end.
the situation
Tried to downgrade my tab from a rom that could not be rooted some ics 4.0.3 build .20 i think it ended with to .15 everything was going fine until it rebooted it just sat on the eepad logo and rebooted ect.
anyway cut a very long night short i have CWM on it version 5.8.2.0 i can get to the fastboot thing but i have a problem now as there appears to be nothing on it i might of deleted somthing i dont remember to tired but theres no data on it no backups nothing.
so its just sitting in CWM atm i cant copy anything to it as it says permission denied i have no way of copying a rom over to it that i know of to get clock work mod to install it when i go to update it with a zip on the sd card the only directory that comes up is clockworkmod
is this beyond help now? or is there somthing i can do please help.
thanks.
Seyah said:
Hey guys have to forgive me very tired spent last 11 hours trying to get this working again but im stuck now and im at my wits end.
the situation
Tried to downgrade my tab from a rom that could not be rooted some ics 4.0.3 build .20 i think it ended with to .15 everything was going fine until it rebooted it just sat on the eepad logo and rebooted ect.
anyway cut a very long night short i have CWM on it version 5.8.2.0 i can get to the fastboot thing but i have a problem now as there appears to be nothing on it i might of deleted somthing i dont remember to tired but theres no data on it no backups nothing.
so its just sitting in CWM atm i cant copy anything to it as it says permission denied i have no way of copying a rom over to it that i know of to get clock work mod to install it when i go to update it with a zip on the sd card the only directory that comes up is clockworkmod
is this beyond help now? or is there somthing i can do please help.
thanks.
Click to expand...
Click to collapse
I will help you when I am at pc later. Get me this info ready please. Power off prime. Hold down volume down and power. When the icons appear for fastboot etc look at the top left where the writing is and at the end of the line with bootloader in it is a long number. Does this number start with a 9 or a 10?
flumpster said:
I will help you when I am at pc later. Get me this info ready please. Power off prime. Hold down volume down and power. When the icons appear for fastboot etc look at the top left where the writing is and at the end of the line with bootloader in it is a long number. Does this number start with a 9 or a 10?
Click to expand...
Click to collapse
Thanks Flumper and thanks for the reply forgive my late reply i have been asleep just got up walked in the front room theres my broken prime
anyway the number at the top starts with a 9
9.4.2.15--20120221 A03
Seyah said:
Thanks Flumper and thanks for the reply forgive my late reply i have been asleep just got up walked in the front room theres my broken prime
anyway the number at the top starts with a 9
9.4.2.15--20120221 A03
Click to expand...
Click to collapse
Sounds just broke not bricker.. if flumpster can't get ya goin then your bricked.... i think its is fixable.
Seyah said:
Thanks Flumper and thanks for the reply forgive my late reply i have been asleep just got up walked in the front room theres my broken prime
anyway the number at the top starts with a 9
9.4.2.15--20120221 A03
Click to expand...
Click to collapse
Ok, you are on the ICS bootloader at the moment. The first thing we are going to do is flash a version of TWRP recovery on there which will allow you to install a rom off the external SD.
Power off the prime and put yourself into fastboot mode by holding power button and volume down the same time until a few icons appear on the screen. At this point press volume down to go over to the usb icon and then press volume up. It will look like the prime has frozen. Plug the prime into pc and make sure you have the drivers installed. If you do not please install them from here. http://forum.xda-developers.com/showthread.php?t=1426502
Next follow this post to flash ICS twrp http://forum.xda-developers.com/showpost.php?p=34477681&postcount=5705
Only use the file in that link to install it while on ICS bootloader. Later on you are going to flash hairybean 1.3 which will take you up to Jellybean Bootloader. If you use this file after that you will brick your tablet.
After you have TWRP installed put a rom Hairybean 1.3 onto the external sd and then go into twrp and select wipe. Factory reset, wipe cache, wipe dalvik and wipe system.
Press back and click install.. Now click the external button to select external sd card and click on the hairybean 1.3 rom.
Follow all instruction in the following post to install 1.3 http://forum.xda-developers.com/showthread.php?t=1674827
Once you have done them all and have now installed Hairybean 1.3 and the new Jellybean twrp and it is all running fine then please feel free to update to Hairybean 1.4.
Hi flumper thanks again for your help..
Im up to the part where i have TWRP installed from you link above, I have downloaded HB 1.3, and i'm a little bit unsure of how to get the rom to the external sd card, I have mounted the external SD-card in TWRP, but adb devices does not list my pad as connected, how do i push the rom over to install? Not sure how to proceed your warning about bricking it has scared the poop out of me
again i can't thank you enough for the help you have provided me.
=== Forgive me i have re-read you post, following instruction's for the 1.3 HB install now will get back to you.
Seyah said:
Hi flumper thanks again for your help..
Im up to the part where i have TWRP installed from you link above, I have downloaded HB 1.3, and i'm a little bit unsure of how to get the rom to the external sd card, I have mounted the external SD-card in TWRP, but adb devices does not list my pad as connected, how do i push the rom over to install? Not sure how to proceed your warning about bricking it has scared the poop out of me
again i can't thank you enough for the help you have provided me.
=== Forgive me i have re-read you post, following instruction's for the 1.3 HB install now will get back to you.
Click to expand...
Click to collapse
I think you have worked it out by now but just put your external sd card into a card reader on your pc and copy it over then put it back in the prime.
Make sure you delete that zip from installing twrp earlier and never use it again.. There will be another one included in the HB 1.3 zip that you extract and flash for a different twrp at about step 8.
flumpster said:
I think you have worked it out by now but just put your external sd card into a card reader on your pc and copy it over then put it back in the prime.
Make sure you delete that zip from installing twrp earlier and never use it again.. There will be another one included in the HB 1.3 zip that you extract and flash for a different twrp at about step 8.
Click to expand...
Click to collapse
Okay Flumper, just a small problem i have encountered i have followed the instructions, I have the 1.3 HB install over on my external SD, I can install it but the first part, wipe all the cache ect but i keep getting errors unable to mount system, unable to mount data, should I just try and install your HB 1.3 or am I going to brick it even more? oh and i don't think the boot loader is unlocked well i don't think it is.
it is unlocked Flumper, i have installed the rom and its booting i did notice a failed to mount /staging at the end but everything installed ok moving on with the install.
== update ==
Flumper your a true boffin! its installing now and will update to 1.4 when its done its working now and i thank you VERY much for your help and support i have popped a £50 donation to red cross to support the people after Sandy and will continue to use your rom.
Thank you so much again and everyone here at XDA.
Karen.
Seyah said:
it is unlocked Flumper, i have installed the rom and its booting i did notice a failed to mount /staging at the end but everything installed ok moving on with the install.
== update ==
Flumper your a true boffin! its installing now and will update to 1.4 when its done its working now and i thank you VERY much for your help and support i have popped a £50 donation to red cross to support the people after Sandy and will continue to use your rom.
Thank you so much again and everyone here at XDA.
Karen.
Click to expand...
Click to collapse
Just a side note I never no which kernel to use and 1.4 has 7 of them which do you recommend?
Seyah said:
Just a side note I never no which kernel to use and 1.4 has 7 of them which do you recommend?
Click to expand...
Click to collapse
Glad you got it all working mate. I recommend clemsyns 1.7 kernel.
Seyah said:
Just a side note I never no which kernel to use and 1.4 has 7 of them which do you recommend?
Click to expand...
Click to collapse
i went with the 1.7Ghz OC kernal good bye Asus bloatware.
Seyah said:
i went with the 1.7Ghz OC kernal good bye Asus bloatware.
Click to expand...
Click to collapse
I gotta stop calling people mate lol. I just presume most of the people I respond to are men, my bad
flumpster said:
I gotta stop calling people mate lol. I just presume most of the people I respond to are men, my bad
Click to expand...
Click to collapse
Don't worry about it Flumper, i'm used to it lol
Seyah said:
Don't worry about it Flumper, i'm used to it lol
Click to expand...
Click to collapse
Keep an eye on the androwook thread. 1.5 will be out next week as we are beta testing it now. It includes the latest patch from asus that came out about 2 weeks ago and other fixes/improvements.
Now that you are on the jellybean bootloader you might want to try a custom twrp I made. It will probably have a more logical layout for you as you've never used twrp before. http://forum.xda-developers.com/showpost.php?p=34359560&postcount=5497
Flash in fastboot the same as before.
P. S. It's Flumpster with an st
flumpster said:
Keep an eye on the androwook thread. 1.5 will be out next week as we are beta testing it now. It includes the latest patch from asus that came out about 2 weeks ago and other fixes/improvements.
Now that you are on the jellybean bootloader you might want to try a custom twrp I made. It will probably have a more logical layout for you as you've never used twrp before. http://forum.xda-developers.com/showpost.php?p=34359560&postcount=5497
Flash in fastboot the same as before.
P. S. It's Flumpster with an st
Click to expand...
Click to collapse
Lol so it's, my mistake Flumpster i'm going to do that now.
*Huggs FlumpSTer for all his help and his alter ego Flumper
Hey all,
I was flashing a new rom and ran into some issues.
I have the new rom on the SD Card, but when I go into TWRP (2.2.0) and go to install,
I can not access the SD card. It shows in the tree, but it is not showing anything on it. I have accidently removed my backup by doing a wipe on everything. Am I done and have to replace it ?
zosopage said:
Hey all,
I was flashing a new rom and ran into some issues.
I have the new rom on the SD Card, but when I go into TWRP (2.2.0) and go to install,
I can not access the SD card. It shows in the tree, but it is not showing anything on it. I have accidently removed my backup by doing a wipe on everything. Am I done and have to replace it ?
Click to expand...
Click to collapse
You should be ok at the moment but we are going to take this one step at a time.
I need to know what bootloader you are on before we progress.
Power off the machine and hold down power down and volume down the same time for about 10 seconds until the icons appear on your screen (usb icon, wipe etc) look up the top left of your screen and there will be text with a long number at the end, it will either start with a 9 or a 10. What is this number?
Also what rom do you want to put on ?
flumpster said:
You should be ok at the moment but we are going to take this one step at a time.
I need to know what bootloader you are on before we progress.
Power off the machine and hold down power down and volume down the same time for about 10 seconds until the icons appear on your screen (usb icon, wipe etc) look up the top left of your screen and there will be text with a long number at the end, it will either start with a 9 or a 10. What is this number?
Also what rom do you want to put on ?
Click to expand...
Click to collapse
I was running cm10 for a helluva long time, but was doing this energy one. states bootloader 2.10 e?
zosopage said:
I was running cm10 for a helluva long time, but was doing this energy one. states bootloader 2.10 e?
Click to expand...
Click to collapse
Hmmm that is not really what I was after.. Let's try another way as I think you will be on ICS bootloader if running an old version of CM10,
Switch on machine and tell me where the Tegra logo is. If it down the bottom center it is ICS bootloader, if it is down the bottom right it is JB bootloader.
flumpster said:
Hmmm that is not really what I was after.. Let's try another way as I think you will be on ICS bootloader if running an old version of CM10,
Switch on machine and tell me where the Tegra logo is. If it down the bottom center it is ICS bootloader, if it is down the bottom right it is JB bootloader.
Click to expand...
Click to collapse
Powered by Nvidia Tegra, bottom center
zosopage said:
Powered by Nvidia Tegra, bottom center
Click to expand...
Click to collapse
Ok, you are still on ICS bootloader.
First of all I would do the nvflash process if you haven't before. http://androidroot.mobi/t3_nvflash/ This can only be done while on ICS and once you have backed up the files created during the process you can never fully hard brick your device.
Then to get you up to the new rom.
Grab the ICS TWRP UPDATER.zip from this thread. http://forum.xda-developers.com/showpost.php?p=34477681&postcount=5705 You will extract the zip file and run the bat file and follow the onscreen instructions to flash it. You will only ever use this once and will allow you to put the Jellybean bootloader and rom onto the external SD to flash it. Never use the file again once you have flashed the Jellybean bootloader as it will brick you. You will flash a JB version of TWRP after the JB bootloader has been installed.
After that is installed you want to go to post 2 here http://forum.xda-developers.com/showthread.php?t=1674827 and follow the insructions for "Upgrade Instructions for ICS"
If you wanted to install energy rom instead of Hairybean just replace the hairybean 1.51 rom in the instructions with energy rom and do the same.
flumpster said:
Ok, you are still on ICS bootloader.
First of all I would do the nvflash process if you haven't before. http://androidroot.mobi/t3_nvflash/ This can only be done while on ICS and once you have backed up the files created during the process you can never fully hard brick your device.
Then to get you up to the new rom.
Grab the ICS TWRP UPDATER.zip from this thread. http://forum.xda-developers.com/showpost.php?p=34477681&postcount=5705 You will extract the zip file and run the bat file and follow the onscreen instructions to flash it. You will only ever use this once and will allow you to put the Jellybean bootloader and rom onto the external SD to flash it. Never use the file again once you have flashed the Jellybean bootloader as it will brick you. You will flash a JB version of TWRP after the JB bootloader has been installed.
After that is installed you want to go to post 2 here http://forum.xda-developers.com/showthread.php?t=1674827 and follow the insructions for "Upgrade Instructions for ICS"
If you wanted to install energy rom instead of Hairybean just replace the hairybean 1.51 rom in the instructions with energy rom and do the same.
Click to expand...
Click to collapse
Thanks for the help. I am trying to get into fastboot USB and the prime jst sits there. I am wondering if I don't have the drivers correct for windows XP. any idea where to get those?
zosopage said:
Thanks for the help. I am trying to get into fastboot USB and the prime jst sits there. I am wondering if I don't have the drivers correct for windows XP. any idea where to get those?
Click to expand...
Click to collapse
When you click up on the USB icon and it says entering fastboot mode and freezes that is normal. That means you are in fastboot.
Look in device manager and see if you have any exclamation marks by anything, if you do then you don't have the drivers installed.
Get them here http://forum.xda-developers.com/showthread.php?t=1426502
Thank you so very much. You saved me tremendously. The ROM is being installed right now and seems to be going fine. And as a plus, I have a pretty cool Recovery now...I was originally thinking that I was going to have to figure out how to explain to the wife that I broke my tab and was going to have to get a nexus 10...
UPDATE, ROM installned and booting right now...now to restore all my apps...
A great learning experience....
Z
zosopage said:
Thank you so very much. You saved me tremendously. The ROM is being installed right now and seems to be going fine. And as a plus, I have a pretty cool Recovery now...I was originally thinking that I was going to have to figure out how to explain to the wife that I broke my tab and was going to have to get a nexus 10...
UPDATE, ROM installned and booting right now...now to restore all my apps...
A great learning experience....
Z
Click to expand...
Click to collapse
I'm guessing you installed my custom TWRP that looks like JB
Glad you got it all sorted mate.. Enjoy
flumpster said:
I'm guessing you installed my custom TWRP that looks like JB
Glad you got it all sorted mate.. Enjoy
Click to expand...
Click to collapse
thanks... now I feel like an idiot as I installed a rom that you are not part of... now that I figured out that 2.12.12 means DEC 2, 2012.. I am going to try the one that you are connected with... thanks again!
Z
zosopage said:
thanks... now I feel like an idiot as I installed a rom that you are not part of... now that I figured out that 2.12.12 means DEC 2, 2012.. I am going to try the one that you are connected with... thanks again!
Z
Click to expand...
Click to collapse
It doesn't matter which rom you install mate. I knew you wanted to install Energy rom when you started and it makes no difference to me.
Energy and Hairybean are both great roms and both based off stock just that Hairybean looks more like stock and Energy is themed.
Try them both and find which one suits you best
Unbrick Prime
It sounds like you have some good help here and hopefully you can get through this problem.. I just wanted to drop my two cents. Good thing to remember is to be on the latest Recovery (as you mentioned TWRP, make sure its always the latest esp. when flashing JB ROM's). Also if you can't unbrick it, head over to this thread here and here where I personally had a lot of assistance unbricking my Prime from a hard brick using nvflash. Good luck.
I'm left clueless here. I just can't get it to boot, no matter what ROM/Kernel i'd flash. It was originally running OOS 2.3.1 but flashing it now won't work anymore. It worked briefly for 1 hour with that AOSP 8.1 but then after trying to flash gapps it stuck again in a bootloop. Sometimes it also freezes and reboots while i am flashing sometimes. I really have no idea what should i do next, hope you can help me.
You need to give more information on which TWRP you have.
Did you upgrade the bootloader at one point ?
OOS 2 is the old one.
You should have upgraded to MM bootloader and the use a TWRP compatible.
If not, you'll have to follow the Mega Unbrick Guide...
Kéno40 said:
You need to give more information on which TWRP you have.
Did you upgrade the bootloader at one point ?
OOS 2 is the old one.
You should have upgraded to MM bootloader and the use a TWRP compatible.
If not, you'll have to follow the Mega Unbrick Guide...
Click to expand...
Click to collapse
I updated the bootloader like over a year ago or so. I also tried 2 different versions of TWRP, now i am using the latest one.
ALSO, very sorry it actually is OOS 3.1.4, not 2.3.1, i just typed briefly what i could remember, i haven't been using this phone for months now but i would like to give it to a relative so there's that. Hope you can help me out, i have no clue why is it acting up like that.
Have you ever think that could be the emmc problem that need to get replaced?
Our phone is old enough...
(just my thoughts btw)
Try to flash official ROM after having wiped everything
Kéno40 said:
Try to flash official ROM after having wiped everything
Click to expand...
Click to collapse
That's what i first tried, mentioned it in the main post.
yayakuya said:
Have you ever think that could be the emmc problem that need to get replaced?
Our phone is old enough...
(just my thoughts btw)
Click to expand...
Click to collapse
I don't know what to make of this, thought maybe anyone else encountered this problem and has a clue.
gabytzu338 said:
That's what i first tried, mentioned it in the main post.
Click to expand...
Click to collapse
You didn't mentionned you wiped everything : System, data, cache, Internal...
Then usb mount to pussh OOS 3 and flash
Kéno40 said:
You didn't mentionned you wiped everything : System, data, cache, Internal...
Then usb mount to pussh OOS 3 and flash
Click to expand...
Click to collapse
I don't really understand what you are trying to say. I did wipe everything and the only way to flash anything is through adb sideload anyway since the device is not recognized as storage while in TWRP. I think I am gonna give up on it, I was gonna sell it but I can't risk having it act up days/weeks after i sold it.