History: It's a 2-month old B40 16GB TF w/o the Dock. It had some issue @1.6GHz but no prolem @1.5.
It had been on PrimeROM from day 1. Recently I tried Clemsyn'sROM_3Final: 1st day was no
issue at all (PimmyCPU locked to 1.4Max). On the 2nd day the battery drained (16hr sleep w/50% battery left)
This is the 1st time I've seen this.
I plugged it in and the TF didnot turn on automatically but it charged to 98% (from 3%) after a few hrs.
I uninstalled PimmyCPU and reloaded SetCPU, set for 1.2GHzMax and went on to read an eBook. After 30min my TF
just hang. So I turned it off (holding the Power-button) and it never wakes up again.
Debug: * Plug & unplug doesn't turn it on automatically (I tried a different charger&cable, I have two TFs).
* Tried different ways to turn it on w/o success. My PC doesn't see it (USB-mode) and I did checked HMDI-to-TV.
* Can't get to CWM.
* I can only get my PCs to see it thru APX (Power & Vol+ works). Remove&replace USB driver multiple times even
tried on a different PC. I attempted NVFlash many times: my PCs could see the device but hung-up at "waiting for
bootloader.ini to initialize". I could see the TF didn't go into APX server-mode (nothing on its screen).
Now: * Just wait for the battery to drain completely, may take days. Don't know if this would help.
* To RMA I need to NVFlash it back to Stock, but can't.
I will take the blame for rooting but don't think it's the cause.
I may do the RMA and hope they change out the dead board and never know it was rooted.
If they found out and refuse the warranty then they can just throw it in the trash-bin for me.
Sorry for this long post. Any comments ? Thanks.
If the board is dead, then they won't find out about rooting (unless they want to go through the trouble of getting at the onboard storage even though the board is dead). I would suggest RMA'ing it and hope that they don't go through that process.
I'm sure they won't because of all the repairs they have to deal with anyway. People just hate those little imperfections
You might have cooked the cpu.
Don't throw it out, you can still use it as replacement parts (like speakers, screen, battery etc..)
makec3rt said:
You might have cooked the cpu.
Don't throw it out, you can still use it as replacement parts (like speakers, screen, battery etc..)
Click to expand...
Click to collapse
Good idea ! But..but, if the RMA isn't going thru it would take $$$ to get it back for spare-parts.
I don't actually need to overclock, I felt my TF was fast enough. I might only OC for a day or two and usually undervolted (max was 1100mV). My TF spent most of the time here running @1GHz.
So far, I don't think the battery has drained yet. No progress. I will wait a couple more days before filling out the RMA form online.
Anyway, I really miss my TF. Luckily, my GTab came to the rescue. Besides the bad viewing angle, this thing is built like a tank. Everything just works as expected. Running Gingerbread blows HC out-of-the-water, maybe due to bloated OS. It's a speed demon even @1GHz.
This is going to sound stupid, but you unzipped the rom into the nvflash folder right (im sure you did, but that is the only thing that came to mind)
hyperxguy said:
Good idea ! But..but, if the RMA isn't going thru it would take $$$ to get it back for spare-parts.
I don't actually need to overclock, I felt my TF was fast enough. I might only OC for a day or two and usually undervolted (max was 1100mV). My TF spent most of the time here running @1GHz.
So far, I don't think the battery has drained yet. No progress. I will wait a couple more days before filling out the RMA form online.
Anyway, I really miss my TF. Luckily, my GTab came to the rescue. Besides the bad viewing angle, this thing is built like a tank. Everything just works as expected. Running Gingerbread blows HC out-of-the-water, maybe due to bloated OS. It's a speed demon even @1GHz.
Click to expand...
Click to collapse
About gingerbread, i wish someone would port that over. I mentioned it once before and everyone was like, why would you want that?
Thanks for the suggestion. I've used NVFlash a few dozens times (mostly with my Gtab) so I could do this while sleeping. I have multiple nflash folders for different devices & situations (root, unroot, root w/ROM1 ....).
I think my TF is 99% dead. It appears that it could get into APX (seeing thru my Win7PC). But it can't turn into APX server-mode. It stuck @bootloader.bin which isn't a part of the ROM.
Mine is dead too as of this morning. I got a splash screen briefly and then the screen went blank. After multiple attempts to reset / long power hold I managed to get it into APX. tried to reflash and got this output from the pc:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 976013/976013 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
usb read error (75): Value too large for defined data type
bootloader failed NvError 0x0
command failure: bootloader download failed
I'm going to try later with an older bootloader but if that doesn't work then this has to be RMA'd.
Ironically my dock is being collected today for the MobileDock Battery Saver issue.
I'm not happy with this product anymore and I'm seriously considering selling and going for another tab.
Oh no, Roach, this suxx, how you gonna provide the best ROM now ? Got a spare one ?
Don't give up on us after so much hard work
Sorry to hear about your problem, Roach. At least you got a little further than I did, my nvflashes would stay at "waiting for bootloader to initialize" forever.
The unit is on its way to Asus for repair.
I hope you hang on to supporting the TF. I was hoping I will get my unit repaired and ready for your Prime1.7 ROM (HC3.2).
Roach's is now working, let's hope he shares how he did
Have you tried using the bootloader.bin that matches your rom? I.e., if you have a 8.4.4.11 rom, use the blob.EBT from the 8.4.4.11 update.
However, the downside, is that I think this will only boot once. When you shut it off, it will be bootloops or APX mode only.
I think nvflash is like a fastboot boot command, and only uses the bootloader to load the system. I don't think it actually writes partition 4. The only way that I found to write partition 4 is use the --create command, but that will wipe your TF completely. If you have backup images, you can flash them by updating the flash.cfg file with all the file names. I wasn't able to flash /data (part 12_USP), but CWM restored it after I restored with nvflash.
I think this tablet is unbrickable, short of a dead cpu. For grins and giggles, I flashed the nvidia android developement ROM- what a nightmare! It was an android zombie! It's set up for hardware buttons and a different screen size. Luckily, APX mode still works and it's back from the dead.
gee one said:
I think nvflash is like a fastboot boot command, and only uses the bootloader to load the system.
Click to expand...
Click to collapse
I could be wrong, but I'm pretty sure that the NVFlash functionality (APX mode) is baked into the Nvidia chipset itself. You can hose everything (including the bootloader) and still be able to bring it back from the dead. I refuse to hack a tablet without it anymore, as it saved my bum from all the times I screwed up flashing my GTablet.
I think all phones, tablets, and other devices should have this mode (or something similar) standard, it would keep noobs from being able to brick their devices and pester the manufacturer for a replacement under warranty (which they shouldn't get).
bud77 said:
Roach's is now working, let's hope he shares how he did
Click to expand...
Click to collapse
Nothing was actually 'wrong' with mine. I had a n00b moment, that's all I'm saying.
I hope that the others in this thread with real issues get them worked out soon though.
Final status
Just got the TF back from RMA, they concluded the case as NoTroubleFound ?!?!
The unit was dead with PrimeROM + OCkernel (I had no way to clean it).
It appears they openned the unit (new frame which no-longer creaks). Everything was wiped clean with stock 8.4.4.11 (except my customed bootanimation is still there but only runs the first portion).
I just did a NVFlash straight to Prime1.7 and everything is great (my customed bootanimation is now gone). I'm back in business (dogged a bullet there).
Related
I got a gTab from TD the other day and I wanted to play around with stock for a bit(the horror) anyways...Its using 4039 my guess as I went to update and it say I have latest version and saw mentions of 4039. I never flashed anything to it yet..
= summary of usage =
I turned it on early before charging and to my surprise it had 0 battery life(unhealthy for the battery), which is weird as batteries are suppose to be around 25% - half charged..so anyways I connected it to the outlet and then powered it on, once it got to ~100% I took it off and used it, afterwards I pressed power button and left, when I came back I pressed power and realized it shut itself off and by that I mean completely off not screen (is this normal?)..throughout the day I realize that it kept shutting itself off after some time..
= end summary =
To the point, I last time I turned it on and it goes on to the birds and gtablet screen and then just shuts off, I can get into recovery and I tried wiping cache and factory reset to no avail, I am guessing next step is NVFlash but is this normal? or do I have a defective unit? (battery is 100%)
Edit: I just ran a downgrade.zip and it started working...but still is the behavior normal? out of curiosity is there a way to check if device is refurbished?
(1) Only you can know if you have a refurb device. Just look for some signs like scratches.
(2) I highly recommend nvflash. If the problem doesn't go away, then perhaps you really do have a defective product.
(3) One possibility is you have a severe case of the sleep of death. This can be solved by flashing a custom kernel. I highly recommend Klemsyn's kernel. He really worked hard on it to stop the sleep of death issue.
(4) Don't forget to repartition to 2048/0 after you put in cwm. This preemptively stop the force closing issue.
(5) Don't forget that 1.1 requires cwm v8 and 1.2 requires cwm 3052 (or something like that, can't remember the number). You will semi-brick your device if you use the wrong version and you will totally brick your device if you flash the wrong branch.
(6) Good luck.
Added by edit.
Me running honeycomb. Me loves it.
goodintentions said:
(1) Only you can know if you have a refurb device. Just look for some signs like scratches.
(2) I highly recommend nvflash. If the problem doesn't go away, then perhaps you really do have a defective product.
(3) One possibility is you have a severe case of the sleep of death. This can be solved by flashing a custom kernel. I highly recommend Klemsyn's kernel. He really worked hard on it to stop the sleep of death issue.
(4) Don't forget to repartition to 2048/0 after you put in cwm. This preemptively stop the force closing issue.
(5) Don't forget that 1.1 requires cwm v8 and 1.2 requires cwm 3052 (or something like that, can't remember the number). You will semi-brick your device if you use the wrong version and you will totally brick your device if you flash the wrong branch.
(6) Good luck.
Added by edit.
Me running honeycomb. Me loves it.
Click to expand...
Click to collapse
yeah I figured out all of that the hard way that day lol..also running honeycomb now ..though too bad no hardware video decode...had to bump up to 1.5ghz to have it stop lagging in 720p mkvs...still subtitles seem to be a bit off :/
So I tried everything in all the other threads and it's still a no go for me. This is extremely disappointing, I was really loving this thing.
I'm scared to even attempt going through Asus's terrible customer service, especially with my TF being rooted and all...
any advice on what I may be able to do?
what happens when you plug it in? Does charger get hot? Try leaving plugged into powered usb overnight.
I had an issue where I left my transformer a week ago plugged into the electricity, and when I came back home - it was out of battery and refused to turn on. I tried plugging into the computer directly but that didn't help either.
Today I went to best buy and plugged it into an adapter on display, and it started working..
When I came back home, I tried my cable again and it suddenly worked!
The moral of the story is it seems the power adaptors are quite flaky. Try to disconnect and connect again..
Also see this thread with some tips on fixing the power adaptor:
http://www.transformerforums.com/fo...er-no-longer-charges-wall-wart-adapter-4.html
I highly doubt the charger is the problem in my particular case because the dock seems to charge fine. Also, my TF died on my when it still had around 80% battery life.
Another thing is that my alarm clock that I have set up on my TF still goes off every morning and the only way for me to turn it off is by repeatedly pressing the power button (this is extremely annoying).
I'm assuming that the screen may have just completely died or something of that sort.
Do you guys have any other advice, or should I just go ahead and attempt to rma it?
thanks it advance
I had this same thing happen to my TF a few weeks ago. The solution for me was to use the tool in this thread: http://forum.xda-developers.com/showthread.php?t=1185104
I used v6.3 for my US 8.6.5.9 rom version. This basic steps I took were to install the APX driver (steps in the thread above), then run the batch file and do 4, 5, & 6. I didn't see anything on my TF screen until the above was completed and then turning it on.
Hope this helps you.
starplaya93 said:
So I tried everything in all the other threads and it's still a no go for me. This is extremely disappointing, I was really loving this thing.
Click to expand...
Click to collapse
Have you tried buying it a few drinks and whispering complements about how beautiful and smart it is into it's microphone?
jmolhava said:
I had this same thing happen to my TF a few weeks ago. The solution for me was to use the tool in this thread: http://forum.xda-developers.com/showthread.php?t=1185104
I used v6.3 for my US 8.6.5.9 rom version. This basic steps I took were to install the APX driver (steps in the thread above), then run the batch file and do 4, 5, & 6. I didn't see anything on my TF screen until the above was completed and then turning it on.
Hope this helps you.
Click to expand...
Click to collapse
Was your transformer already rooted? It seems as if this tool is for rooting transformers, and mine is already rooted with a custom rom loaded onto it.
Can you please walk me through exactly what you did to get this process to work?
I'm pretty desperate as of right now!
Edit: So apparently my TF is still capable of connecting to my PC and I can view all of the folders on the internal memory as well as put it in APX mode, does this mean there is still hope for me?
Please guys, if anybody has some insight on how I could possibly fix this, it would mean more to me than you can imagine.
starplaya93 said:
Was your transformer already rooted? It seems as if this tool is for rooting transformers, and mine is already rooted with a custom rom loaded onto it.
Can you please walk me through exactly what you did to get this process to work?
I'm pretty desperate as of right now!
Edit: So apparently my TF is still capable of connecting to my PC and I can view all of the folders on the internal memory as well as put it in APX mode, does this mean there is still hope for me?
Please guys, if anybody has some insight on how I could possibly fix this, it would mean more to me than you can imagine.
Click to expand...
Click to collapse
Bump /:
10char
starplaya93 said:
Was your transformer already rooted? It seems as if this tool is for rooting transformers, and mine is already rooted with a custom rom loaded onto it.
Can you please walk me through exactly what you did to get this process to work?
I'm pretty desperate as of right now!
Edit: So apparently my TF is still capable of connecting to my PC and I can view all of the folders on the internal memory as well as put it in APX mode, does this mean there is still hope for me?
Please guys, if anybody has some insight on how I could possibly fix this, it would mean more to me than you can imagine.
Click to expand...
Click to collapse
I am very interrested in this thread as I have the very same problem.
Asus proposed to RMA it but I fear that they might find some trace of the previous root as I unrooted "blindly"
blabox said:
I am very interrested in this thread as I have the very same problem.
Asus proposed to RMA it but I fear that they might find some trace of the previous root as I unrooted "blindly"
Click to expand...
Click to collapse
yeah, that is what i'm worried about as well.
What number did you contact for the RMA?
Well apparently my only option is to RMA the device.
I went ahead and un-rooted it with the BRK toolkit, however after un-rooting it said that I have to load a stock rom and recovery image onto it. How do I go about doing this without turning it on and flashing the zip in recovery?
Do you all think ASUS will even notice it is rooted and if so what steps should I take to ensure that there is no proof of root?
Please help me a bit on this one guys.
I had the same issue with mine last week. Appeare dead but would connect to PC APX mode and could view SD card contents.
When looking at the screen with a flashlight, the text was visible. The unit was actually working but the backlight had died.
Had to get it replaced with new one from place I bought it from on their product replacement scheme. great except its a new one that can't be rooted yet.
Sitting patiently for that to be released so I can go back to playing....
starplaya93 said:
Was your transformer already rooted? It seems as if this tool is for rooting transformers, and mine is already rooted with a custom rom loaded onto it.
Can you please walk me through exactly what you did to get this process to work?
I'm pretty desperate as of right now!
Edit: So apparently my TF is still capable of connecting to my PC and I can view all of the folders on the internal memory as well as put it in APX mode, does this mean there is still hope for me?
Please guys, if anybody has some insight on how I could possibly fix this, it would mean more to me than you can imagine.
Click to expand...
Click to collapse
Yes, my TF was rooted and running a custom ROM. When running the batch file that is in the package in the other thread I referenced, I did steps 4, 5, and 6. Then rebooted and it was fine. If you can get the APX driver installed and your computer will recognize it, then try those steps using the tool. Once I rebooted, it just loaded my same ROM as if nothing had happened.
Of course a hardware failure would cause the same thing (backlight or LCD not working, etc...) but in my case it was a software or booting issue and the above fixed it. If you try what I did and still nothing then RMA is probably your only option.
i had this problem too, in my case it was a defective power button. had to push it real hard to get the pad turned on ... rma fixed it ....
i have the same problem also and it turned out to be the power button my solution was just to keep pressing it haha and then it worked strangely enough. ive read somewhere that it it gets misalligned somehow. i guess i have 2 options either send it back or fix it myself at the moment im just living with it.
it works somedays then otherdays it takes a few pushes lol
My case seems to be none of the above.
I tried checking if it was an issue with the back light and put a flashlight up to it in a pitch black dark room but I can't see anything on the screen whats so ever, regardless of the angle I put it in.
I also don't think it is the power button because like I said, i'm able to put he tablet in APX mode and take it out of APX mode as well at will by pressing the power and volume up button.
Thirdly, I tried the root kit several times (version 7) and while it's doing it's job of rooting and un-rooting my TF, there still is no change in the functionality of the screen.
so i'm pretty much sol. I already placed in an RMA to asus, now I just have to ship it off (asus has by far the worst customer service that I have ever seen).
My final question would be is there anyway to load a stock rom and recovery image without being able to turn the tablet on? I'm able to unroot it with the rootkit, but it says that I still need to load a stock rom and whatnot.
If somebody can point me towards directions as to how I go about doing this, that would be great.
Thanks for all the help guys.
So, I RMA'd my tablet, that was a horrible nightmare, but it's finally over, yay the end. I had actually done it for the dead pixels. I no longer have dead pixels, though my screen now has a slightly warm tint, which is obnoxious, but I guess that's better than dead pixels. Asus sent my TF back with a broken USB connection, so I had to send it back a second time. I discovered said broken USB connection halfway through an nvflash. That was fun. Long story short, I'm pretty sure they replaced the motherboard.
Anyway, I have a B6O, and I was rooted before. If they replaced the motherboard, I assume they replaced the processor, but I could be wrong, and also an idiot, so I thought I'd ask. Anyone been through this before? I'm wondering if I could now have an unrootable B6O. I know there's an SBK detect program, but now I'm a little gun-shy after everything I've been through with this, even though I was pretty much a flashaholic before. Anyone have thoughts/recommendations on where to start? I've heard conflicting reports on just attempting the nvflash, since someone said APX bootloop is possible, and I really don't want that.
Anyway, another question: is there any way to sort of calibrate the display somewhat? The slightly yellow tint is a bit irritating, and I was wondering if there was anyway to offset it a bit. The color temperature is just a bit too warm for my taste.
Thanks all.
Someone did say they can not root a B70 that was rootable before it was rma
what i have read is that they replace the entire main-board including wherever the sbk is located and they put in one with v2 so you will have to wait untill that is rootable. and i would run the sbk detect program it cant do anything bad to the transformer it just looks through some system files
So, when I run the SBK detect program, on both my Arch machine and my Linux Mint laptop (just to check that this wasn't something weird with my Arch desktop, since I'm still learning Arch) it says "Segmentation Fault." Wtf. (ia32-libs are installed) So...I'm stumped. I had initially assumed it was because it didn't know what to do with a B6O, since why would a person with a B6O run an SBK detect program EVER, since you would automatically assume you could root. It's really only the people with B7Os who would need to check, since some are rootable and some aren't.
So, I don't know. If anyone has any ideas, that'd be awesome, but I give up for now. Guess I'll just run stock! It's not so bad.
Hi people,
I'm just looking for a bit of friendly advice really. I know there are similar threads about both of my separate issues but I just want a bit of help weighing up my options.
I've been enjoying my used TF300T ('unwanted gift') for about 6 months and had CM10 running on it. I have had (very) intermittent problems with the touch screen of the type I've seen described on the forum, where it will lose touch input completely but will come back on if you reboot it or turn the screen off/on etc. This has probably happened about 10 times in 6 months, and never persisted beyond a reboot.
Last week, whilst I was away from home and perhaps less inclined to do the proper forum-trawling, I had the problem reoccur but it was persistent. No touch input at all. Perfectly functional within the dock though. I figured the first thing I would try was a factory reset. I booted recovery only to realise that I had the lovely TWRP touch recovery installed and couldn't use it. At this point, I decided that this was very probably a hardware issue if touch didn't work in the recovery or the main OS (though there may be things I don't know that still muddy the water here??).
I opened it up to have a look if there were any cables needed securing etc. At this point, I realised I was definitely on my own because the 'Warranty void...' sticker had already been broken ('Unwanted gift', eh?). I played with the cable a bit and could get it to behave differently but only succeeded in getting 'ghost' input allover the place. I figured that at least it was receiving some input now and crossed my fingers that a factory reset would 'recalibrate' it in some way.
In desperation and not wanting to pay too much in roaming data on my phone, I didn't come here and do the reading I should have done. I just installed CWM recovery and used that to do a factory reset (It's not compatible, it hung, I powered it off and now I've killed my bootloader. No recovery, no fastboot, only APX. I've now read this scenario a number of times on the forum :crying. So, with my excuses made and story told, my questions are as follows:
1) Am I correct in saying this brick is unrecoverable at the minute? (I didn't create the blob.bin I need to use wheelie and get nvflash access. This blob.bin is device specific and I can't unpack it from a cm10 or ASUS download? I think I probably only need to reflash the bootloader, so might not need bricksafe.img??)
2) If I were to have ASUS reflash this, I believe it comes in somewhere below $100 and could be worthwhile if the touch problem is a software one.. Do you think the touch problem is hardware or software?
3) If the screen is a hardware problem, can anyone tell me which part I might need to replace?
4) If it needs reflashing and a part replaced (either by me or an ASUS engineer), should I really be looking at selling this for parts and getting a new one economically speaking? Are any of the parts I have actually useful to anyone?!
Many thanks for reading a long and complicated post. If it cheers you up, the garage also told me my car isn't worth repairing this week!
I believe that you have a hard brick.
Asus can fix it but they normally just replace the motherboard and charge in the region of $250 for this service.
Your device will come back locked and you a lot of people have found the unlock tool no longer works. Probably due to serial not matching MB.
Best option is sell individual working parts on eBay whilst they have some value and you might get $200+ back. Or sell the unit as faulty for $100+
Sorry for the bad news.
Thanks for the input, sbdags. In terms of selling the parts individually, is it just really the screen and digitizer that have any value? ..and the dock, I guess.
asus service have tools to unlock force recovery mode and reflash it but it is easy to said us motherboard replacement to get to much money lol
My photon is currently stuck in a boot loop. I replaced the digitizer a few days ago and can't boot to system since the replacement. It's unlocked and was running Cyanogenmod 11 and would boot to the animation and after 10ish seconds would freeze and reboot. I tried wiping via TWRP and flashing Cyanogenmod 12 with no luck. Here the the contents from my apanic_console when trying with cyanogenmod 12: http://pastebin.com/gTC5sYiL
Thanks of the help
I assume this line is the tell of the issue.
Code:
<0>[ 29.110086,1] Kernel panic - not syncing: Fatal exception
<4>[ 33.836746,1] SMP: failed to stop secondary CPUs
<3>[ 33.839829,1] mbm_version=0x0000109b
<0>[ 33.841477,1] CPU type is ACPU PVS: Fast
<0>[ 34.064916,1] Timestamp = 1271386292.619
<0>[ 34.069525,1] Current Time = 04-16 02:51:32.619, Uptime = 34.061 seconds
<0>[ 34.071265,1] RAM: Elpida, S4 SDRAM, 1024 MB, MR5:0x03, MR6:0x00, MR7:0x00, MR8:0x18
Some issue with the cpu. I haven't overclocked it ever either.
Have you tried to RSD Lite back to stock?
A bit of a pain sure but if it fixes your issue then who cares...
hockeymikey said:
I assume this line is the tell of the issue.
Code:
<0>[ 29.110086,1] Kernel panic - not syncing: Fatal exception
<4>[ 33.836746,1] SMP: failed to stop secondary CPUs
<3>[ 33.839829,1] mbm_version=0x0000109b
<0>[ 33.841477,1] CPU type is ACPU PVS: Fast
<0>[ 34.064916,1] Timestamp = 1271386292.619
<0>[ 34.069525,1] Current Time = 04-16 02:51:32.619, Uptime = 34.061 seconds
<0>[ 34.071265,1] RAM: Elpida, S4 SDRAM, 1024 MB, MR5:0x03, MR6:0x00, MR7:0x00, MR8:0x18
Some issue with the cpu. I haven't overclocked it ever either.
Click to expand...
Click to collapse
The "SMP: failed..." is irrelevant here.
From the log it shows that interrupt 107 is failing/not enabled. That interrupt is mapped to MDP (Mobile Display Processor) so it probably means that digitizer replacement messed up something, e.g. something is loose, something got damaged during the process, new part itself is damaged/malfunctioning...
Check connections, test the old one to see if it bootloops the same way...
mrvek said:
The "SMP: failed..." is irrelevant here.
From the log it shows that interrupt 107 is failing/not enabled. That interrupt is mapped to MDP (Mobile Display Processor) so it probably means that digitizer replacement messed up something, e.g. something is loose, something got damaged during the process, new part itself is damaged/malfunctioning...
Check connections, test the old one to see if it bootloops the same way...
Click to expand...
Click to collapse
Why would that be causing an issue yet works fine in recovery?
arrrghhh said:
Have you tried to RSD Lite back to stock?
A bit of a pain sure but if it fixes your issue then who cares...
Click to expand...
Click to collapse
Tried, didn't work, still in bootloop.
Detached the new digitizer and still had the same issue. The bracket holding the middle ribbon in broke in half before. It still holds the ribbon in place fine so I doubt that's the issue.
Still having the same issue, haven't been able to resolve it yet.
Bumped. Still haven't been able to fix this.
Bump still isn't fixed.
hockeymikey said:
Bump still isn't fixed.
Click to expand...
Click to collapse
Dunno why you keep bumping the thread, the issue is obviously related to the hardware replacement / cables / etc. It's not a software issue.
arrrghhh said:
Dunno why you keep bumping the thread, the issue is obviously related to the hardware replacement / cables / etc. It's not a software issue.
Click to expand...
Click to collapse
It's not the digitizer because I still got a kernel panic with the old one so I'm looking for further input.
hockeymikey said:
It's not the digitizer because I still got a kernel panic with the old one so I'm looking for further input.
Click to expand...
Click to collapse
Cables connecting the digitizer?
It's a hardware issue for sure. Keep looking at that... Phone repair is such a delicate process, it's very easy to break something else.
I am experiencing a similar issue; I was about to post my own thread until I saw your post.
I have a FreedomPop (refurbished Sprint) Motorola Photon Q 4G LTE and the only mod I did was too root it. I didn't customize the bootloader, recovery, ROM, or any of the hardware. One day, all of the sudden, it was just stuck in a boot loop after a normal reboot. It would show the Motorola logo then during the FreedomPop ROM logo it would stop and reboot.
When I first received the phone from FP, I noticed a dent/discoloration spot on the screen like it had been damaged in some way (pressed on too hard or drop). I also noticed that the touch screen would be glitchy/less responsive when I was using it while it was charging on USB. But I didn't think too much of it at the time.
I thought the boot loop problem was software related so I flashed the phone with Sprint's stock android ROM using RsdLite, but I got the same errors in RsdLite that you did. It would flash without any problems but during the final step of rebooting it would be stuck in the boot loop.
I was also able to unlock the bootloader from AP Fastboot mode and install TWMP and CWM and then try to flash CyanogenMod 10. The flashing was successful since I see the new logos from the new ROM's but it would stop and reboot.
My hypothesis is that some component of the touch screen (digitizer, cable, etc) was on it's last legs (thanks for sending me your trash FreedomPop) and that it finally failed after 2-3 months of normal usage. And during the boot up process if it detects any type of hardware fault/failure, it'll try to reboot.
I confirmed that problem revolves around screen (digitizer, or cable connecting it) because I was not able to use the touch screen to navigate TWMP, but I am able to navigate in Fastboot and CWM using the power and volume buttons.
I was thinking about replacing the digitizer or even the entire screen component, but it seems that from your post that it's a gamble as to whether that would work or not. It probably isn't even worth the time or effort.
I had another keyboard slider phone fail on my before, so I probably avoid these types of phones in the future as hardware problems are prevalent.
TL;DR touch screen component hardware failure is causing boot loop. replacing it probably won't fix it. definitely not worth the time and effort to try.
anonkneemass said:
I am experiencing a similar issue; I was about to post my own thread until I saw your post.
I have a FreedomPop (refurbished Sprint) Motorola Photon Q 4G LTE and the only mod I did was too root it. I didn't customize the bootloader, recovery, ROM, or any of the hardware. One day, all of the sudden, it was just stuck in a boot loop after a normal reboot. It would show the Motorola logo then during the FreedomPop ROM logo it would stop and reboot.
When I first received the phone from FP, I noticed a dent/discoloration spot on the screen like it had been damaged in some way (pressed on too hard or drop). I also noticed that the touch screen would be glitchy/less responsive when I was using it while it was charging on USB. But I didn't think too much of it at the time.
I thought the boot loop problem was software related so I flashed the phone with Sprint's stock android ROM using RsdLite, but I got the same errors in RsdLite that you did. It would flash without any problems but during the final step of rebooting it would be stuck in the boot loop.
I was also able to unlock the bootloader from AP Fastboot mode and install TWMP and CWM and then try to flash CyanogenMod 10. The flashing was successful since I see the new logos from the new ROM's but it would stop and reboot.
My hypothesis is that some component of the touch screen (digitizer, cable, etc) was on it's last legs (thanks for sending me your trash FreedomPop) and that it finally failed after 2-3 months of normal usage. And during the boot up process if it detects any type of hardware fault/failure, it'll try to reboot.
I confirmed that problem revolves around screen (digitizer, or cable connecting it) because I was not able to use the touch screen to navigate TWMP, but I am able to navigate in Fastboot and CWM using the power and volume buttons.
I was thinking about replacing the digitizer or even the entire screen component, but it seems that from your post that it's a gamble as to whether that would work or not. It probably isn't even worth the time or effort.
I had another keyboard slider phone fail on my before, so I probably avoid these types of phones in the future as hardware problems are prevalent.
TL;DR touch screen component hardware failure is causing boot loop. replacing it probably won't fix it. definitely not worth the time and effort to try.
Click to expand...
Click to collapse
I'm going to re-tackle this issue and see what new solutions I can come up with. If memory serves me right I could use the digitizer just fine to navigate TWMP (if my memory is correct).