well the title says it all
but let me explain further
so ive been running cm10.1 on my galaxy tab 10.1 the P5113 model to be exact and ive been running the ICS bootloader and then on the cm10.2 thread i saw the JB bootloaders and decided to flash the P5110 bootloader......then everything hit the wall and pretty much broke D:
so then i wanted to try a few JB roms but upon rebooting to system on a lot of ROMs my tablet will just sit there at the device slash screen longer than usual then it will turn to a full screen of pink/green and a few other colored lines and just sits there ._. is it bricked? i hope not D:
what do i do? ive tried using ODIN to reflash stock to the JB firmware the same thing happens D: it seems that my device was fine on the ICS bootloader but ever since that update its been like this D: please help
have you tried kies? if not do this, BEFORE CONNECTING tablet TO PC start kies, go to upgrade and initialisation. enter your tablets model number and serial number. put tablet in download mode, NOW CONNECT tablet TO PC. this should force kies to upgrade your firmware
did that work?
A friend of me had same problem he solved it by going back to stock (rom & Kernel ) then he did a ota update and when the tablet said that update was ok he rebooted and he installed cwm and cleared cache and dalvic cashe and problem was solved
I actually got got running because it wouldnt boot even on an official stock firmware but for some reason it booted up after I went into the stock samsung recovery and wiped data factory reset so idk
Sent from my GT-P5113 using XDA Premium 4 mobile app
Factory reset is always the best initial move after flashing and getting a bootloop. When people panick and start flashing other things it drains the battery and corrupts files making i even harder to boot when a factory reset usually is all that is needed to fix a bootloop after a flash
Sent from my GT-I9300 using XDA Premium 4 mobile app
Hi guys, I am new here, I am now finding help anywhere about my Note III recent problem...
My note III is SM-N9005 Malaysia version, I did root it with CF Auto Root and I had been using it without problems until yesterday morning,
This is my case :
I realized my alarm was written "Clock has been not responding" and I lost my network service, then I tried to restart my phone,
Since I restart, it became worst, my phone went into boot loop and sometimes freeze on the "Samsung Galaxy Note 3" screen,
But in a few times of reboot, it will be able to boot into homescreen, but still no service for the network, and everything processes work extremely slow, even freezing and crashing!
What I tried to do to fix it :
-I went to the Samsung service center, and the technician said that my warranty is voided (Ofcourse I knew it), and he told me that this problem is due to software problem instead of hardware.
-I did flash my kernel with stock kernel again which was downloaded from Sammobile, but it did not fix my problem,
-And I tried to hard reset and factory reset of my phone, it did not help too,
-I am also tried to clear cache and dalvik cache and reboot the device, it didn't seems working...
I have already done what I could but I still yet to fix my phone, what should I do now, any experts can guild me?? T^T
Thank you
KelvinEclipse said:
Hi guys, I am new here, I am now finding help anywhere about my Note III recent problem...
My note III is SM-N9005 Malaysia version, I did root it with CF Auto Root and I had been using it without problems until yesterday morning,
This is my case :
I realized my alarm was written "Clock has been not responding" and I lost my network service, then I tried to restart my phone,
Since I restart, it became worst, my phone went into boot loop and sometimes freeze on the "Samsung Galaxy Note 3" screen,
But in a few times of reboot, it will be able to boot into homescreen, but still no service for the network, and everything processes work extremely slow, even freezing and crashing!
What I tried to do to fix it :
-I went to the Samsung service center, and the technician said that my warranty is voided (Ofcourse I knew it), and he told me that this problem is due to software problem instead of hardware.
-I did flash my kernel with stock kernel again which was downloaded from Sammobile, but it did not fix my problem,
-And I tried to hard reset and factory reset of my phone, it did not help too,
-I am also tried to clear cache and dalvik cache and reboot the device, it didn't seems working...
I have already done what I could but I still yet to fix my phone, what should I do now, any experts can guild me?? T^T
Thank you
Click to expand...
Click to collapse
have you done a EFS backup? it helps if you run into problems like this....
check here...http://forum.xda-developers.com/showthread.php?t=2298104
this works on note 8 though
welard said:
have you done a EFS backup? it helps if you run into problems like this....
check here...http://forum.xda-developers.com/showthread.php?t=2298104
this works on note 8 though
Click to expand...
Click to collapse
I didn't really know about EFS while I root my phone, I just knew it recently due to my current issue, so I didn't backup it....
Is there any other solution??? Or could I recover my EFS eventhough I didn't do a backup??
BTW, thx for reply~
KelvinEclipse said:
I didn't really know about EFS while I root my phone, I just knew it recently due to my current issue, so I didn't backup it....
Is there any other solution??? Or could I recover my EFS eventhough I didn't do a backup??
BTW, thx for reply~
Click to expand...
Click to collapse
check your internal card or sd card for a folder called Backups or something similar, if your running a custom rom normally EFS is automatically stored there if your custom rom does do EFS backup automatically at install....if not do a search on the forum for EFS RECOVERY or re-flash your rom it may help or may not, but im sure it wont though...
also read though the link i sent you there maybe some think there that may help you
you can try to do install new firmware with odin 3:09 kitkate see how it behaves ....
ANDROIDXFOREVER said:
you can try to do install new firmware with odin 3:09 kitkate see how it behaves ....
Click to expand...
Click to collapse
Its not bricked if its still working. Have you tried turning on your phone without a sim card / sd card inserted?
also try *#06# to see if your imei number is presant..
try flashing stock rom
in the same boat hope u get it sorted, i just flashed the omega v14 onto my note and its stuck on the first screen
yulaw5110 said:
in the same boat hope u get it sorted, i just flashed the omega v14 onto my note and its stuck on the first screen
Click to expand...
Click to collapse
Reboot into recovery and wipe cache partition and then scroll to advanced and wipe dalvik cache, then reboot your phone
Sent from my SM-N9005 using XDA Premium 4 mobile app
Thanks guys for the replies
-I went for a search for the backup folder in either of the storage mentioned by I didn't see a file called "backup"... I think I deleted it since the factory reset I've done yesterday, I went to many forums hat talk about EFS, and it wont help my problem cos all of them are talk about "Backup/recover", where I didn't backup my EFS earlier...
-I tried for the IMEI code, that's the reason I know about EFS, it shows "null/null", and most the information are showing unknown, such as baseband version, IMEISV, IP Address, Bluetooth Address.
-My current situation is whatever I flash into my phone, it just wont help, the problem didn't improvise at all...
Thanks..
KelvinEclipse said:
Thanks guys for the replies
-I went for a search for the backup folder in either of the storage mentioned by I didn't see a file called "backup"... I think I deleted it since the factory reset I've done yesterday, I went to many forums hat talk about EFS, and it wont help my problem cos all of them are talk about "Backup/recover", where I didn't backup my EFS earlier...
-I tried for the IMEI code, that's the reason I know about EFS, it shows "null/null", and most the information are showing unknown, such as baseband version, IMEISV, IP Address, Bluetooth Address.
-My current situation is whatever I flash into my phone, it just wont help, the problem didn't improvise at all...
Thanks..
Click to expand...
Click to collapse
download Stock firmware from sammobile or samsung updates
turn phone off, boot into recovery mode wipe data/factory reset, wipe cache partition
turn phone off, boot into download mode
use odin v 3.09 load your downloaded firmware into AP, check update boot loader box, don't check anything else and click start.
once it finishes flashing, it will reboot by itself.
if it fails then you might want to repeat the process above one more time.
if still fails u might want to do emergency recovery via kies.
Good luck and hope this helps.
doodydood said:
download Stock firmware from sammobile or samsung updates
turn phone off, boot into recovery mode wipe data/factory reset, wipe cache partition
turn phone off, boot into download mode
use odin v 3.09 load your downloaded firmware into AP, check update boot loader box, don't check anything else and click start.
once it finishes flashing, it will reboot by itself.
if it fails then you might want to repeat the process above one more time.
if still fails u might want to do emergency recovery via kies.
Good luck and hope this helps.
Click to expand...
Click to collapse
Thanks for the reply
I have tried the odin method and it didn't work...
Now I am trying for the kies emergency recovery method, and I will reply if there are any improvements...
Hi guys, I think have some new clues to determine my problem now
I flashed a custom recovery into my phone this morning,
and I realise that my /system, /efs and /firmware-modem is unmounted,
I tried to mount them, it was successful, but when I reboot the device, the problem still there,
Boot loop, no IMEI, no Baseband Version, Lag Processes,
and I went back to recovery again, I realised they have been unmounted again...
Any idea what is the problem guys??
Thx
doodydood said:
download Stock firmware from sammobile or samsung updates
turn phone off, boot into recovery mode wipe data/factory reset, wipe cache partition
turn phone off, boot into download mode
use odin v 3.09 load your downloaded firmware into AP, check update boot loader box, don't check anything else and click start.
once it finishes flashing, it will reboot by itself.
if it fails then you might want to repeat the process above one more time.
if still fails u might want to do emergency recovery via kies.
Good luck and hope this helps.
Click to expand...
Click to collapse
Hi there,
I have tried the kies emergency recovery method, but it was unsuccessful,
My note 3 was connected to the kies, but when I run Emergency Firmware Recovery,
My device was instantly disconnected with kies
And I have also tried the Firmware Upgrade and Initialisation,
The Kies showed me that my device is not supported with initialisation...
Anything I should do??
Thx
speedyjay said:
Reboot into recovery and wipe cache partition and then scroll to advanced and wipe dalvik cache, then reboot your phone
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i actually found a different kernal in the omega thread and that seemed to sort it, thanks tho
Not sure quite what's happened, I'm assuming a hardware flash issue, but if anyone has any ideas how to fix this, do chip in.
Using nexus 7 (unlocked, but stock and unrooted) when it crashed. Since crash, it looks decidedly read only. It'll boot and you can do a limited number of things, but then it's liable to crash again. Nothing you do is stored, so if you uninstall an app, or change a setting, it'll be back to how it was before after reboot.
Used fastboot to wipe the partitions, but nothing has any effect. Doing a factory reset doesn't wipe user data. Wiping user data from fastboot does nothing. Flashing another recovery does not work, and the stock recovery remains. I can boot twrp using fastboot.
Is this just a hardware fault and I'm stuffed?
Thanks for any and all help,
Uhm... Good afternoon.
I really don't know what happened to my XT907. I was playing Castle Clash, and then, suddenly...
- Smart Launcher Pro stopped
- GApps stopped
- Messenger stopped
- Amazon MP3 stopped
- WhatsApp stopped
And 4 or 5 more apps stopped. I nned to say what I wasn't using any of that apps but Smart Launcher Pro and WhatsApp.
So I selected the common Power Button... Power Off... Then I used the common Power Button for Turn On my XT907...
Stuck on the boot animation. It makes the sounds as receiving WhatsApp messages and that, but it's eternally on the boot animation (it isn't a bootloop)
What to do in this case?
(I need to add something else: I used the volume up button and every time I use it, the cellphone vibrates)
Try using House of Moto and reflashing your FXZ (assuming you're on a stock ROM) using the Universal or Keep Data option. If that doesn't work, unfortunately, you may have to factory reset or do a full FXZ flash. If you're okay with wiping your data, you can try a factory reset through recovery (works on stock)
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk
xKroniK13x said:
Try using House of Moto and reflashing your FXZ (assuming you're on a stock ROM) using the Universal or Keep Data option. If that doesn't work, unfortunately, you may have to factory reset or do a full FXZ flash. If you're okay with wiping your data, you can try a factory reset through recovery (works on stock)
Sent from my RAZR M on BlissPop Lollipop 5.0.2 from Tapatalk
Click to expand...
Click to collapse
Believe me: I don't have trouble with the apps... I have important chats on WhatsApp but it's recoverable. I experimented with wipe cache and the phone immediately reboot
Good morning.
After almost 3 years with no problems with a XT907, I have again an issue with it (this time, my father's one). Again, I come to you requesting help.
It all started with all apps crashing over and over. With an old XT907 I have for emergencies, the common fix method is flashing VZW_XT907_4.4.2-KDA20.62-15.1_1FF.xml.zip with RSD Lite v6.1.5 and all solved.
I tried that method with my father unit, and when it started again, all process were still crashing. I thought it was still nothing (just a harder issue), and tried flashing VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF_SVC.xml.zip, just deleting all his data, to fix it.
When the process ended, it turned on and it had still the same problem. In this point, I got worried the /system and /data partitions got locked
I re-started, went to stock Recovery, and wiped system and cache. Then, went to Fastboot a third time and tried again flashing VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF_SVC.xml.zip. Guess what? Still the same problem
The phone turns on, but ALL apps keep crashing over and over. I can't even take an screenshot, as it immediately reboots.
Someone know what happened with it? And... how to fix this issue?
To make things worse
Fastbook Locked
No Root
Last 4.4.2 stock ROM
by twrp try make Wipe Data Or Repair File System, if not done mybe your internal memory Currpted