Hi,
I'm a little nooby at all this, trying to learn better.
I started with a fully working, Galaxy S2, which I rooted ages ago. I did a factory reset on it, then the phone would not boot - it goot stuck at the Samsung Logo. (Probably due to the battery running out during the new user set up).
So I installed slimbean ROM 4.3 build 1 (put it on the SD card, installed by holding volume up+ power+ menu button).
After that, it still won't boot. This time, it got stuck on the SlimBean logo, instead a Samsung Logo.
So I installed Siyah-v3.3.2-CWM kernel. Now, after the first boot screen, it goes blank (no ROM boot screen).
Umm. Maybe I'm making more of a mess. But the most important thing is that I understand how this all works. Please don't send me to a guide, I've already read lots (they make a lot of assumtions about knowledge level, and are often really wordy which muddles things up in my mind.
I probably installed the wrong kernel for the version of slimrom I have....
Help ! ?
Please someone reply
Absolutely do not bump threads after an hour. This isn't your personal tech support hotline.
Good job keeping the forum in order, boss. Must be lonely at the top.
Related
Verizon Galaxy Tab 10.1 4G LTE (sch-i905)
So I got this tablet from a friend who said it was bricked, said I could have it if I got it working. So I plug it in and it turns on no problem, strange. wiped tablet and added a couple apps. Got busy at work and the tablet drain power. That's when I got to see it bricked, but still not sure why it booted for a bit for me.
Symptoms:
Boots to Samsung Galaxy Tab 10.1 splash screen (not the animated one after), sits there for ever.
Boots to Odin update mode
When booting to recovery I get a blank, back lit screen and nothing ever.
I've tried:
-Pushing clockwork mode to fix recovery
-I've had a hell of a time finding stock firmware for some reason (it isn't on sammobile), but I did find one eventually. I pushed it to the tablet via Odin, and it was successful, but rebooted to blank black back-lit screen. Have to hard boot and hold power buttun until I see the splash screen to get that far. I followed the guide on rootzwiki reposted on icsforums - www icsforums com/forum/showthread / 13525 (sorry new member can't post links)
-Followed another guide that involved draining battery completely, no go.
I don't care what firmware I end up on, or if I can use LTE (I won't anyway)
I'm a network engineer so I'm tech savy, but not heavy on Android OS. I'm looking for anything else I can try. I saw another method involving heimdall suite, but can't find the files for my model.
Any help or guidance is greatly appreciated.
@Juicebox4242
I had this problem on my gt-p7510...
What I ended up doing was wiping my sdcard..I must have had something corrupt in my file system or a kernel issue( still not sure which )..
Since you have no recovery..I think you can use odin to repartition ( I CAN NOT STRESS ENOUGH THAT THIS IS JUST A GUESS )..I have not tried it..but i will search after this post to confirm..I also believe there is a way using ADB..again not sure..
I just wanted to post this so you would know somebody was looking and to maybe give you a couple ideas to follow up on...I'll search around and see what I find
Edit...I believe ADB will only work with usb debugging checked...But you can flash a stock rom in odin with re-partition checked..you need a .pit file....I think...
Edit...Here is a link to a stock rom thread for you're device..It seems to have helped a couple people with their soft-bricked devices..just follow directions in OP..no repartition checked. I cant even find a .pit file to do a re-partition with for you're device..
http://forum.xda-developers.com/showthread.php?t=1342995 Let me know if this works for you..
Thanks for the post!! Really appreciate it.
That firmware is the one I found in the end and tried. Odin pushes it ok, but then still doesn't boot. In fact after pushing that firmware it boots to backlit blank screen, but when hard reset boots to splash screen.
I tried a pit file I found that I thought was the right one, but it failed when I used that so it must have been wrong.
Juicebox4242 said:
Thanks for the post!! Really appreciate it.
That firmware is the one I found in the end and tried. Odin pushes it ok, but then still doesn't boot. In fact after pushing that firmware it boots to backlit blank screen, but when hard reset boots to splash screen.
I tried a pit file I found that I thought was the right one, but it failed when I used that so it must have been wrong.
Click to expand...
Click to collapse
I have the exact same problem as you, except sometimes I can't my tablet to boot. I know it is a software problem because before I was messing with recovery yesterday, everything was working just fine. All I wanted to do was restore to factory settings and instead ended up bricking the device... If you find / know the answer, please do share.
Juicebox4242 said:
Verizon Galaxy Tab 10.1 4G LTE (sch-i905)
So I got this tablet from a friend who said it was bricked, said I could have it if I got it working. So I plug it in and it turns on no problem, strange. wiped tablet and added a couple apps. Got busy at work and the tablet drain power. That's when I got to see it bricked, but still not sure why it booted for a bit for me.
Symptoms:
Boots to Samsung Galaxy Tab 10.1 splash screen (not the animated one after), sits there for ever.
Boots to Odin update mode
When booting to recovery I get a blank, back lit screen and nothing ever.
I've tried:
-Pushing clockwork mode to fix recovery
-I've had a hell of a time finding stock firmware for some reason (it isn't on sammobile), but I did find one eventually. I pushed it to the tablet via Odin, and it was successful, but rebooted to blank black back-lit screen. Have to hard boot and hold power buttun until I see the splash screen to get that far. I followed the guide on rootzwiki reposted on icsforums - www icsforums com/forum/showthread / 13525 (sorry new member can't post links)
-Followed another guide that involved draining battery completely, no go.
I don't care what firmware I end up on, or if I can use LTE (I won't anyway)
I'm a network engineer so I'm tech savy, but not heavy on Android OS. I'm looking for anything else I can try. I saw another method involving heimdall suite, but can't find the files for my model.
Any help or guidance is greatly appreciated.
Click to expand...
Click to collapse
Did you ever get this fixed? I've had the same problem for months. I just gave up and put it away. I recently fixed a Galaxy Tab 2 and now I want to see if anyone else was able to fix this i905 not booting issue.
did anyone know the solution of this question
As previously stated I am a complete noob when it comes to flashing android devices.
Here is the problem I am faced with: I recently rooted, and unlocked the bootloader on my atrix hd (ATT)
Since then I tried installing cm10.1 multiple times on the secondary "Rom slots" within the bootloader, without any success. So I finally decided to go for it and install cm10.1 in the "stock rom" slot, Prior to doing this I did a back-up using Rom manager. Aand now I seemingly can't even boot into recovery mode, every time I restart my device it simply goes to the cyanogenmod blue ring thingy and gets stuck! (I have left it for 15-20 mins thinking it might be some kind of installation process..) But apparently it's not and i've broken my smartphone lol. Anyway i'd really appreciate some help fixing this problem, a step-by step guide would probably work best..!!! I have both windows 8 and Ubuntu installed on my pc, just saying..Don't know if it's relevant information and may simplify fixing my problem...Thanks in advance guys and girls
i've even tried holding down all three physical buttons and it simply takes me back to the same screen!!!
you could try something like this:
http://forum.xda-developers.com/showthread.php?t=2434726
.. and you are sure, that you can not enter the recovery menu??
official motorola guide, how to enter recovery menu:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/60620/action/auth
.. adb could be your last possibility, if everything else fails, google it, you'll find many answer
hi,
"maybe you saw this post elsewhere but i was forwarded here so the rest is the same"
have elephone p2000 with some custom rom on it and working stock recovery. than i flash new rom called resrom 1.5, rooted BUT internal storage is access denied and 0kb. Just to say that my usb port is broken and will be hard to replace it because someone was trying to make it work and totally screwed up.
So anyway I cannot connect to a pc and fix things. Next, cant access recovery, tried to flash new one but to no avail. I am still rooted but even when using some apk to flash new rom or recovery i get msgs like "not enough space" or nothing is happening.
info on the phone:
ELEPHONE P2000 MT 5692
4.4.2
MOLY.WR8.W1315.MD.WG.MP.V35.P8.2014/11/03
KERNEL 3.4.67 [email protected] #1
BUILD P2000_20150228_RESTORN
Play store ok, calls and the rest is fine, apk i am using: mobileuncle, rashr, auto flasher but nothing gets job done, flashyfy doesn't work and many others. I was looking into init files saw some guide but don t want to mess things even more so i gave up, also wanting to flash boot.img but no proper or functional apk for it.
sometimes on phone start stuck in a loop of screen turn on for 20 sec and then off and its like that until i remove battery, all before rom logo, same thing if i try use buttons combination for recovery or whatever i press in any combination nothing changes.
This is not my first smartphone but is of this kind and funny companies, had problems before with Sony, Samsung but in this extent never, always find YOU guys everybody clever in some fields and as a community more than THE BEST, as you can see i dont post or seek answers by asking, i rather research until now. I fell hopeless, useless and never more stupid, or i m just tired of looking for the answer. In some other case i would give it to my child to play the games an to hell with this phone but its my wife's and she dont want to by a new phone for some reason. Help me to be the man of the house again, kidding, loosing it....
I think I gave you overall picture of the phone state and someone might show me the way to have fully working phone. I forgot, if you are wondering how do i charge battery, well I take it out twice a day and charging on the base of other broken phone, that part i did cover, help me with the rest.
p.s my SD card is working most of the time so this is my only connection to a pc....
Deleted
Hey lovely ladies and gents,
So here is the situation: I have an LG Optimus l70 MS323, which until yesterday was with a stock ROM. I banged my head against the wall, trying desperately to follow a guide and root it, along with trying to unlock the bootloader until I watched a video (in Spanish. Thank you high school spanish!) which used flashify to flash a CWM and boot to the custom recovery. I loved it, since that meant that I would be able to finally flash an official Cyanogenmod OS. The first ROM that I flashed was cm-13.0-20160121-NIGHTLY-w5.zip, which worked and made me feel SO HAPPY (I almost yelled Eurika for the sake of historical comedy). I then went ahead and installed an Superuser-SU binary update through the CWM recovery because I wanted to keep on having root. Then I installed a nano gapps package for ARM, Android 6.0 with some minor complications (mostly the "Setup Wizard" crashing every 2 seconds). I rewiped and reinstalled Cyanogenmod through CWM, flashed gapps on the same go, and made a little backup through the recovery menu. I booted up successfully to be met with that buttery-smooth GUI of Marshmallow (ugh, so good.) I decided to go ahead and fetch some apps from the Play Store, such as Messenger and ROM manager. I saw that the Cyanogenmod Update Center had pushed out a notification that the newest nightly snapshot is already downloaded and decided "Meh. What new features have been added? Let's reboot and reinstall." At that point it was 4:40am (keep in mind that I've been trying to get the goddamn phone to cooperate since ~10pm) and I noticed that the boot sequence takes up a lot longer and told myself "It's probably taking a bit longer than usual, it's normal." I put the phone next to my head, hoping that it's going to be ready to use in the morning.
Fast forward to 8:07 am. Bootloader is still going, phone is so hot it can cook an egg.
GNAAAAAAAAAAAAAAAAAAAHHHH. WHY YOU GOTTA DO DIS TO ME PHONE?!??! WHY!?!
SO, the CURRENT situation:
1. Whenever I press the power button, it starts off normally. According to my definition of bootloop, it's stuck in a bootloop.
After hours of staring that goddamn cyanogenmod mascot do you realize that it's going to boot itself into the booting oblivion.
2. I don't have access to CWM. I have tried holding down the power buttons with godknowswhat combinations (I like to call them the Naruto Jutsu of pure despair). Maybe I should hold the buttons for 2 milliseconds longer and it might work. *Sigh*
3. I don't think that I can use fastbood or adb. My computer doesn't see the phone. (GNAAHHAHASDJFLSKDHFSLJHLKJ.)
4. I am totally clueless about what I should do or try. I've basically softbricked my phone and don't know how to unbrick it.
So, now that you see that saying that I'm frustrated is truly an understatement, what do you suggest I do?
In advance, I'd like to thank you SO MUCH for even giving a sh!t about my problem.
Other misc info: I have a 32GB SD card on which I have all the different tools I have used throughout this journey.
I am willing to have it back on stock ROM. My biggest goal is to somehow boot into CWM recovery. From there on, I will be able to deal with it. Until I come back to this forum, begging for mercy.
Have u tried using LG suite or LGUP u need to go to LG 's firmware page I'm not sure about this phone but it worked w my k7 about 100 times also helped unlock it. Check out the LG k7 forum lots of guys on there that use the lgup program and can help
Hi guys, sorry if I posted this at the wrong place.
I have a Lenovo s860 and it went into a bootloop. It was stock and all so I thought that I can have my files recovered if I just bring it to a service center so they can get the files first before wiping it or maybe even fixing the bootloop without wiping the device. Well, the thing is, the guy at the service center screwed up and now, when I try to turn it on, I still see the boot screen (Lenovo, powered by Android) but the next screen is like an television with bad signal.
I'm familiar with rooting and flashing ROMs, I've tried it on my Galaxy S2 (yeah I know, it was way back), but I think things are still more or less the same: I need to be able to boot into recovery mode in order to root the device. However, when I tried the Power Button + Volume Up, or any combinations of the Power Button and the Volume Buttons, it just goes straight to the dead screen, I get no response whatsoever.
I also tried to check if adb can detect it, however, it didn't seem to be able to do so. I'm using a MacBook Pro so I know I don't have to install any drivers, I also code Android Apps so I have a background on this.
I think my only option would be to flash the ROM on this dead device but I don't know how to do that. I've also seen some posts that suggest doing some things (I forgot the specifics) while the battery is drained, so what I'm doing for the mean time is to leave the phone open and let it drain which might take ~2 days.
Does anyone know how to flash a ROM on a bricked device? Thanks for any leads.