Hello fellow XDA members! I am a Noob.
So I believe I have a Bricked Galaxy Note 10.1. Model GT-N8013
I Rooted Stock ROM, and flashed Collective Edition 5 Dark Side.
So heres what happened, everything seemed fine, until I made a mistake, I was Pimping my ROM with the PimpMyRom app. Every change seemed fine and my note worked, but when i saw the double boot screen slide in the app, i did what it said, i have the imf support or something like that. Then after i had the ''support'' needed, i clicked install button on the double boot slide, it seemed to do something and requested nothing, so i went ahead chose a second clip, and clicked set as second boot screen. It said it wont take effect until the 3rd boot, so i rebooted 3x, but at the third time, it was stuck at the boot screen with the galaxy note 10.1 logo ! It did not start or did anything, over time it would turn off and automatically reboot, but it would get stuck again !.
To attempt to fix it, I Booted into recovery (CWM) and did everything i could. I wiped nearly all cache, factory reseted, then out of fear, i flashed the stock firmware ROM from Sammobile website, with ODIN, and to my knowledge, it got worse!! It booted, seemed to do something then in the logo screen it got stuck once again!! Stock recovery says unable to mount /efs, i don't believe EFS is completely corrupted, I left it stuck for awhile and it shut down in like an hour. Help, what can i do to fix this!?!?!?!
Device cannot boot up.
I could boot into recovery and download mode only.
I thought that I too had bricked my 8013 the past weekend. Trying to do something that I shouldn't. It took me a bit of work and a lot of worry (my wife gave me my 8013 for Xmas and if I had to tell her that it was now a doorstop, she would have killed me). I used this method to get back to stock and then was able to work my way back to the ROM I use. I disremember in which order I Odin'd things, but in the end was able to un-brick. All I can say is give it a shot.
jusliloleme said:
I thought that I too had bricked my 8013 the past weekend. Trying to do something that I shouldn't. It took me a bit of work and a lot of worry (my wife gave me my 8013 for Xmas and if I had to tell her that it was now a doorstop, she would have killed me). I used this method to get back to stock and then was able to work my way back to the ROM I use. I disremember in which order I Odin'd things, but in the end was able to un-brick. All I can say is give it a shot.
Click to expand...
Click to collapse
i did what u said...but all i got is i able to get through the logo but without seeing anything only able to hear the sound. any other tip? i got the same problem as above.
Hello.
I've looked in the other threads involving boot loops but couldn't find a solution.
I have an AKAI 7" Tablet (Model AK8460) running Android 4.0.3. It ran fine till I got into my head
that I must find a way to display Greek diacritics on my tablet's browser since I study Ancient Greek.
My device was not rooted and I would be afraid doing so even if I knew how.
After trying both font installer and iFont, I copied Times new roman bold from my PC to the custom folder under ifont
and then tried setting it as the default font. I didn't see any message that the process was completed, but the device rebooted
and ever since. it is stuck in a boot loop. This didn't happen with Arial Unicode MS or SBL Greek. In both cases, the device rebooted
with no boot loop (though diacritics weren't displayed but that's another matter).
The tablet has this pinhole reset but I don't quite understand at what point during the boot I'm supposed to use it
and for how long.
Your help is much appreciated.
One website had some recovery methods for various devices but it seems AKAI is a company with
no official website or brochures with listed combo-buttons to get into recovery mode.
The pinhole reset is just like a restart button on a PC. It wouldn't revert the tablet to its factory settings and
is still stuck in a boot loop.
Please help.
Never mind. Got a new one off the store. This all fiasco started because there is no support for more unicode characters
as there is on the IOS Apple devices. I know some LG and Samsung devices have the ability to change the system font
without rooting. I'm not gonna risk another bricked tablet.
I know its a late answer but it might help someone : I have an Akai k711hd ( I belive made by Lava, xtron model ) holding down the power button for like 8+ sec or so rebooted and factory reset my tablet.
Sent from my GT-I9100 using XDA Free mobile app
Hello. I Was wondering if someone can help me with a dilemma......... i recently got my mega a month ago. I then decided to root my mega (As i do with all my android devices)The rooting process worked out great. The phone booted.....Everything's all peachy! root was successful! After about 3 weeks i wanted to record my screen. By the way i was running kitkat on my mega. So i installed a screen recording program. i wanted to record the screen so i started the recording..... but it wasnt recording. it kept saying an error message i think it when like gpu is not supported and change to cpu something like that! i thought nothing of it... so i changed the settings to gpu then to cpu (Not knowing what i was doing) after it failed to record again i threw the towel in and quit. i then played one of my mobile games(FNAF2) after i lost the game i went back to the homescreen and the homescreen was acting up... it was in landscape mode when i had the phone upright. it was bugging me to the point where i just rebooted my device. i tried rebooting my device BUT IT WAS IN A BOOTLOOP! i had no idea what was going on. So i tried to restore the backup and it was restored but it was still in a bootloop. at this point i was freaking out! when i went home that day i put the device in download mode and flashed the stock firmware but it failed and didnt work. but when the phone rebooted it booted up and my phone was on activation screen and it was in a different language. then i soon found out that my touchscreen wasnt responding! neither was the home button or back button. i really dont know whats going on. kies does not work i tried emergency firmware initializing and kies didnt read it i tried reinstalling kies and my phones drivers 4 times and it was a no go...... but i finally found a english firmware and i flashed it but it failed and said something like dev_not supported or something so that didnt work either..... i booted up my phone and the language was back to english and my touchscreen wasnt working neither was my home buttons or anything. i also tried installing custom roms but everytime i try to install them it says it completed installing but when i boot up my phone its the same activation screen. i really need help anything that can help will be greatly appreciated. also everytime i boot up it always says set warranty bit:Kernal
Hi guys, I have an Allview P5 Mini-Android 4.0.4
Few days ago I rooted it and everything was fine. Then I started to unninstall apps and I think I unninstaled a wrong one because is sais all the time Android.process.acore has stopped unexpectedly and it doesn't show my bottom bar anymore. All I can do is getting apps to main screen and acces them.
So I learned how to install a new rom to fix those problems and make my phone faster. But I am stuck at the recovery to avoid toggle signature verification. I tried a lot of recoveries because I dont find an ,,official" one for my phone. The cwm versions that I tried blocked my phone to the logo and some of the twrp versions make my screen flash with white and black line verticaly and horizontaly.
Is there anything I can do to make sure that the recovery mod starts? Or is there any other way to install a new Rom?(without accesing recovery mode)
I am pretty desperate, I don't know what else to do. Any suggestion or method is welcome.
Thanks in advance!
Well... some days ago I tried to install a known game from playstore, Soccerstar (a friend challenged me on the game) and when i started it I just got a notification that said UI system stopped working witch means UI crashed. I closed the phone (with the hope at reboot it will all be ok). When i power it on it wasnt getting over the android animation at boot. And now the phone it's stuck in bootloop from then. I never unlocked bootloeader or rooted or used devs option .... I tried from the recovery mode to reset the phone . That didn't work.... And the phone cant connect to the pc only with the option in recovery mode"Apply update from ADB" So now i ask you for a solution (If i need it i'm ok with changing the android).
Any clues what should i do than trow it in a garbege can?