Help please.
I purchased 2 thrive tablets from best buy on a recent holiday from uk to usa (one for myself and one for my father in law).
I recently installed the update on my own without a problem. However when my father in law installed it on his thrive it got into a boot loop when rebooting. It keeps booting with the words "booting recovery kernel image".
When i do the vol/power switch on and pick the box icon to reset the same boot loop happens. I can use the tablet by doing the vol/power switch on and choosing the android icon but dont want to do this everytime i use the tablet.
Since i live in the uk and bought the tab in the usa I dont know what my warranty rights are.
Any help would be greatly appreciated.
william40 said:
Help please.
I purchased 2 thrive tablets from best buy on a recent holiday from uk to usa (one for myself and one for my father in law).
I recently installed the update on my own without a problem. However when my father in law installed it on his thrive it got into a boot loop when rebooting. It keeps booting with the words "booting recovery kernel image".
When i do the vol/power switch on and pick the box icon to reset the same boot loop happens. I can use the tablet by doing the vol/power switch on and choosing the android icon but dont want to do this everytime i use the tablet.
Since i live in the uk and bought the tab in the usa I dont know what my warranty rights are.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
OK, let me get this right. Your Father-in-Law did the update and when it rebooted it got to "Booting recovery Kernel Image" and hung. If you shut it down and try to boot it, it still comes up and says the same thing.
If I have this right, it has not installed the update. It has hung up tryig to reboot into recovery to apply the update. You said you can go into recovery and select boot and it will boot fine. If this so, open the Service Station and see if you can select the update again. With any luck, you sould be able to get it to redownload and install it again and fix the issue.
You also said you did a reset and it still came up with the message. Did you do a full factory reset? If not, do that and it should boot up as it did the firat day it was turned on. Also, if you have done this, try clearing the cache and reboot to see if that fixes the issue.
Thanks for the reply
I did try the service update again from the service station but the tablet shuts down then reboots with the same problem i.e. the" booting recovery kernel image loop"
I also tried the full factory reset from the settings but same boot loop again.
I also tried the reset by clicking on the open box icon when you turn on the tablet with the vol up/power buttons but again i get the boot loop
william40 said:
Thanks for the reply
I did try the service update again from the service station but the tablet shuts down then reboots with the same problem i.e. the" booting recovery kernel image loop"
I also tried the full factory reset from the settings but same boot loop again.
I also tried the reset by clicking on the open box icon when you turn on the tablet with the vol up/power buttons but again i get the boot loop
Click to expand...
Click to collapse
Sounds like you covered all th normal stuff. The final option I can give you is to go here and download my Thrive Easy Flash Tool. Once you have it, follow the readme file to load the adb drivers on your PC. I am assuming you have a Windows PC, if not, let me know. Once you get the ADB drivers loaded and operational, flash the Clock=WorkMod recovery to the device. Once it is loaded, you can download AustereGrims Thrive 0029 Stock images or rooted images and load them. Since it is your Father-in-Laws Thrive, I would load the stock images. After that is done, the device should boot just fine and be updated to the latest load.
Let me know if you have any other problems.
Mod Edit: Offsite links requiring registration removed.
Thanks Paul.
Will give it a go.
william40 said:
Thanks Paul.
Will give it a go.
Click to expand...
Click to collapse
No problem. Try ThriveForums.org. Think you find a lot of good info and people.
Many thanks for your help Paul.
Tablet is now starting up as normal.
Only prob is I now have no wifi. I get a wifi error in the wireless settings and cant add any networks.
Afraid I'm a bit of a dummie when it comes to this rooting and flashing lark.
Thanks again
william40 said:
Many thanks for your help Paul.
Tablet is now starting up as normal.
Only prob is I now have no wifi. I get a wifi error in the wireless settings and cant add any networks.
Afraid I'm a bit of a dummie when it comes to this rooting and flashing lark.
Thanks again
Click to expand...
Click to collapse
I am glad you have it almost working. It looks like you have the wrong version of the boot image or wrong version of the system image. If all you did was my root tool, then you have a new boot image with the older system image. That is why the WiFi says error. What you now need to do is get the file from AustereGrim that I gave you a link to. If you used the stock image of his and have the WiFi error, then he did not update the stock image with the correct boot image. In that case, just use my tool to flash a stock boot image. If you need more assistance, send me your Email via PM and I will get back to you to help.
Hi All,
Need your help. I tried setting up a corporate Exchange Account on my Iconia (rooted, running Honeyvillain 1.05). After set up of the account, I was asked to encrypt the table (policy from the corporate server). I followed the prompts to start the encryption process, entered a password, and then the device rebooted. It then was stuck on the screen with "Android" on it. I waited 30 minutes, and nothing. I forced a restart and then was presented with a green android (with a belt?) and prompting me for my password. After entering the password and hitting "OK" it would then immediately reboot and stop, again, at the screen with the white "Android". I tried wiping and restarting but nothing. I then tried installing a different ROM, but again was prompted for my password. This time (virtuous galaxy rom) it didn't actually restart, but just froze on the screen with the green android robot with the belt looking thing. I've tried running the unbricking process using the update.zip method, but still cannot get past the screen prompting me for my password. Would love your help with this! Am I out of luck?
Thanks,
-T
I use encryption with my tablet, and switched from various stock roms without problems, but I even didn't try with the custom roms, surely it will fail and loose all my data. The only thing I can think for you repair your tablet is to try to flash a stock rom and see if it boots, if not, then you have to erase everything from the tablet. There is a post saying to boot holding the power+vol up keys and then move the lock switch several times on and off, so it deletes everything on the tablet like a hard reset.
After you do that I will recommend stick with the stock rom (rooted if you want, it doesn't disturb the encryption) and encrypt the tablet again, it took quite a time to do it, specially if you have many data in the internal memory.
Hope it helps you.
Hi There,
Thanks for the reply. In the meantime, I actually found some instructions on how to do a factory reset (volume+ and power, then release power, then toggle screen lock twice) and I managed to revive it! I had previously tried installing the update.zip mentioned here: http://androidforums.com/acer-iconia-tab-a500/345419-un-brick-acer-iconia-tab-a500.html, and after a factory reset, the tab booted into this stock EMEA ROM.
Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!
redbay1 said:
Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!
Click to expand...
Click to collapse
That is the norm for fastboot, it doesn't go past that screen.
It may not make a difference, did you try to boot to recovery via Power+Volume Down buttons?
Greetings Khaos64,
Yes, I've tried booting with Vol-Down+Power but the phone does not start.
With volume-up+power, I get the Fastboot splash screen but the phone does not respond to any input.
I tried selecting "bootloader" from the reboot menu but I get the same thing: Reboots and after a second, the phone reboots again normaly and into OxygenOS.
Is there a way to verify if the bootloader or recovery is corrupt and maybe reflash the stock recovery onto the phone?
Thanks for your input!
You may just want to go straight to oneplus support since everything is stock and only 2 weeks they should be able to get you updated or replace it.
If you'd like to be more hands on... maybe something below can help.
So your phone isn't recognized/no commands acceptred from your computer when booted to fastboot?
Such as unlocking your bootloader and booting into twrp... "fastboot boot yourfilename.img" or maybe flashing it.
Make sure OEM unlocking is selected in Developer options.
If you can't do that then this may not work but is worth a shot.
http://forum.xda-developers.com/showpost.php?p=62973446&postcount=2
These may also be something to look into:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
I did try to contact Oneplus for support but I am not the one who purchased the phone. Long story short, it was a gift from my girlfriend that she bought off of someone. The phone was new in box and was a warranty replacement. I would have to contact the seller and go trough him for support unfortunately.
Thanks for the different suggestions!, I will fiddle around with it this afternoon while the kids are having their mid-day nap and I'll get back with the results
Thanks again for the help, it's greatly appreciated!
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Congratulations hope you enjoy the phone
Sent from my ONE A2005 using Tapatalk
redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
Glad one was able to help you do it. :good:
redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
HI there,
I am having the exact same issue with my oneplus 2. Unfortunately i know almost nothing regarding these android thingy. I know it has been almost 2 years, would you mind guide me through the steps? I would appreciate it so much.
Thanks.
Hi,
**Long Story**
I'm new here - I refrained from posting as I know a repeat post can p*** people off but I can't find my problem or fix it.
My own Sony was stolen a week ago - My brother in law kindly gave me his old S5 as a back up phone.
He has never had any problems with it EVER. I did a factory reset (from the settings menu) to clear his data and straight away I was in a boot loop (Handset vibrates, Samsung logo displays, blue LED, vibrates, handset switches off.. over and over again) the only way to stop this is to remove the battery. I cannot enter recovery mode but I CAN enter download mode. According to the settings the handset was running the latest version of lollipop.
I took the phone home anyway, thinking I could fix it - leaving the battery out in my pocket.
When I got home, I put the battery in and the phone turned on, unfortunately I forgot to put the sim card in - so I removed the battery, put in the sim card and... Boot Loop!
At this point I was really frustrated so I left the battery out and went to sleep. I woke up in the morning, put the battery in and it worked fine, all day, then all of a sudden the phone switched itself off and now I'm back in a boot loop and this time it isn't wanting to work again.
I have:
- Flashed with stock roms using Odin (5.0 & 4.4.2) - Yes, I used the correct firmware for my handset.
- Flashed with Kies to the latest firmware
- In desperation, tried the "Bash your power button against a hard, flat surface" trick
- Shouted at the handset
None of these have worked and every post I have found says to put the phone in recovery mode, I CANT. When I try, the blue "Recovery Booting" text is displayed, but just restarts anyway...
Weirdly and at random times, twice, the phone has powered on while plugged into my laptop, but the screen is blank, I get message sounds and the soft keys below the screen light up, but the screen is blank.
Any body have any idea?!?!! I'm vaguely techy, however not with this kind of thing. Any help would be much appreciated. What confuses me is there was no problem before I did the factory reset.
didscub said:
Hi,
**Long Story**
I'm new here - I refrained from posting as I know a repeat post can p*** people off but I can't find my problem or fix it.
My own Sony was stolen a week ago - My brother in law kindly gave me his old S5 as a back up phone.
He has never had any problems with it EVER. I did a factory reset (from the settings menu) to clear his data and straight away I was in a boot loop (Handset vibrates, Samsung logo displays, blue LED, vibrates, handset switches off.. over and over again) the only way to stop this is to remove the battery. I cannot enter recovery mode but I CAN enter download mode. According to the settings the handset was running the latest version of lollipop.
I took the phone home anyway, thinking I could fix it - leaving the battery out in my pocket.
When I got home, I put the battery in and the phone turned on, unfortunately I forgot to put the sim card in - so I removed the battery, put in the sim card and... Boot Loop!
At this point I was really frustrated so I left the battery out and went to sleep. I woke up in the morning, put the battery in and it worked fine, all day, then all of a sudden the phone switched itself off and now I'm back in a boot loop and this time it isn't wanting to work again.
I have:
- Flashed with stock roms using Odin (5.0 & 4.4.2) - Yes, I used the correct firmware for my handset.
- Flashed with Kies to the latest firmware
- In desperation, tried the "Bash your power button against a hard, flat surface" trick
- Shouted at the handset
None of these have worked and every post I have found says to put the phone in recovery mode, I CANT. When I try, the blue "Recovery Booting" text is displayed, but just restarts anyway...
Weirdly and at random times, twice, the phone has powered on while plugged into my laptop, but the screen is blank, I get message sounds and the soft keys below the screen light up, but the screen is blank.
Any body have any idea?!?!! I'm vaguely techy, however not with this kind of thing. Any help would be much appreciated. What confuses me is there was no problem before I did the factory reset.
Click to expand...
Click to collapse
Who is your service provider? Is the phone unlocked? Where did you get the stock firmware from?
Cryceratops said:
Who is your service provider? Is the phone unlocked? Where did you get the stock firmware from?
Click to expand...
Click to collapse
Thanks for the reply!
Service Provider - o2 UK
Stock from sanmmob
Phone is not unlocked
I did my best to try & get the firmware for my particular service provider but sammob and a few of the other sites use those awful restricted speed file sharing sites.
didscub said:
Thanks for the reply!
Service Provider - o2 UK
Stock from sanmmob
Phone is not unlocked
I did my best to try & get the firmware for my particular service provider but sammob and a few of the other sites use those awful restricted speed file sharing sites.
Click to expand...
Click to collapse
Did you try the one I linked to you or a different one?
Cryceratops said:
Did you try the one I linked to you or a different one?
Click to expand...
Click to collapse
Only just saw that - I didnt - thank you.
I will try now but may take a while to get back to you while I wait to download.
Try flashing the PIT file along with the stock ROM in ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract to .pit - add to PIT section in ODIN, add ROM to AP or PDA section, flash them both at the same time
*Detection* said:
Try flashing the PIT file along with the stock ROM in ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract to .pit - add to PIT section in ODIN, add ROM to AP or PDA section, flash them both at the same time
Click to expand...
Click to collapse
Thanks, did that, now the phone has started but it stuck at the first "Powered by Android" screen, not restarting but can't go any further and still cant get into recovery.
didscub said:
Thanks, did that, now the phone has started but it stuck at the first "Powered by Android" screen, not restarting but can't go any further and still cant get into recovery.
Click to expand...
Click to collapse
Try flashing just the ROM again, and then try booting into recovery, and factory reset
Or try flashing TWRP 2.8.7.0 with ODIN, and then boot into recovery and factory reset
Use this guide (Don't worry about the SuperSU part if you don't need root, and ignore the reactivation part as you can't boot the phone yet - start at No.3)
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Are you flashing the latest Lollipop ROM too?
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM
*Detection* said:
Try flashing just the ROM again, and then try booting into recovery, and factory reset
Or try flashing TWRP 2.8.7.0 with ODIN, and then boot into recovery and factory reset
Use this guide (Don't worry about the SuperSU part if you don't need root, and ignore the reactivation part as you can't boot the phone yet - start at No.3)
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Are you flashing the latest Lollipop ROM too?
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM
Click to expand...
Click to collapse
flashed TWRP 2.8.7.0 - Doesn't go into revovery:
Recovery is not SEANDROID ENFORCING
Set Warranty Bit : Recovery
I was flashing with G900FXXU1BOJ1_G900FOXA1BOJ1_G900FXXU1BOJ1_HOME.tar.md5
didscub said:
flashed TWRP 2.8.7.0 - Doesn't go into revovery:
Recovery is not SEANDROID ENFORCING
Set Warranty Bit : Recovery
I was flashing with G900FXXU1BOJ1_G900FOXA1BOJ1_G900FXXU1BOJ1_HOME.tar.md5
Click to expand...
Click to collapse
Did you follow the guide I linked?
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Pull the battery after flash, do not allow the phone to reboot first etc?
Because that error is usually associated with you allowing the phone to reboot Automatically after flashing TWRP
*Detection* said:
Did you follow the guide I linked?
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Pull the battery after flash, do not allow the phone to reboot first etc?
Because that error is usually associated with you allowing the phone to reboot Automatically after flashing TWRP
Click to expand...
Click to collapse
Pulled as soon as it said Pass.
This is so confusing, is the Stock firmware that you've linked to in Mega the same as the one I have downloaded?
Will retry with TWRP again. BRB
didscub said:
Pulled as soon as it said Pass.
This is so confusing, is the Stock firmware that you've linked to in Mega the same as the one I have downloaded?
Will retry with TWRP again. BRB
Click to expand...
Click to collapse
BOJ1 yea, same one
Try different versions of ODIN, 3.09 up to 3.10.7 (Maybe even 3.07)
*Detection* said:
Did you follow the guide I linked?
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Pull the battery after flash, do not allow the phone to reboot first etc?
Because that error is usually associated with you allowing the phone to reboot Automatically after flashing TWRP
Click to expand...
Click to collapse
Definitely didt let it reboot & pulled the battery. Tried it twice to make sure.
I am downloading the Stock firmware that you have linked and will try that, is there any reason why it started to reboot constantly after I factory reset? It can't be hardware because there was never a HW problem before I reset it. I don't suppose you want to pop down from Durham and fix it?! lol
didscub said:
Definitely didt let it reboot & pulled the battery. Tried it twice to make sure.
I am downloading the Stock firmware that you have linked and will try that, is there any reason why it started to reboot constantly after I factory reset? It can't be hardware because there was never a HW problem before I reset it. I don't suppose you want to pop down from Durham and fix it?! lol
Click to expand...
Click to collapse
To London? wanna pay the plane fare? lol
If you got that firmware from Sammobile, the one I linked you to is the same one, that's where I got it from, you could try some different droid versions, try a KitKat ROM too
Not sure why it would boot loop after you factory reset it, if reactivation lock was left on, you should still have managed to get to the welcome screen, but then be locked out of the phone until you entered his samsung account login
Sounds like something bugged out during the reset, and didn't reset properly, or corrupted one of the partitions, which the PIT file should have fixed
Stock recovery is cr4p though, I've ended up with a bootloop just clearing caches from it before, and had to flash TWRP to clear them properly, then flash stock on top again just to get it to boot
*Detection* said:
To London? wanna pay the plane fare? lol
If you got that firmware from Sammobile, the one I linked you to is the same one, that's where I got it from, you could try some different droid versions, try a KitKat ROM too
Not sure why it would boot loop after you factory reset it, if reactivation lock was left on, you should still have managed to get to the welcome screen, but then be locked out of the phone until you entered his samsung account login
Sounds like something bugged out during the reset, and didn't reset properly, or corrupted one of the partitions, which the PIT file should have fixed
Stock recovery is cr4p though, I've ended up with a bootloop just clearing caches from it before, and had to flash TWRP to clear them properly, then flash stock on top again just to get it to boot
Click to expand...
Click to collapse
OK - Sorry for the delay but unfortunately I had to do stuff - I would have happily sat and tried to fix it all day.
So, I did spend some time on it earlier and a few things happened.
I reinstalled different firmwares, and also tried TWRP 2.8.7.0 a few times with different versions of Odin but nothing would work.
I reinstalled the firmware BOJ1, nothing
Tried PIT again, nothing
Then, after trying PIT I got the Firmware error and connected to Kies... It worked, but now I just have a blank screen (another seemingly common issue with these paperweights) - Unsure what to do now, the phone is on, i can call it, find it with device manager but the screen is just blank. FML.
didscub said:
OK - Sorry for the delay but unfortunately I had to do stuff - I would have happily sat and tried to fix it all day.
So, I did spend some time on it earlier and a few things happened.
I reinstalled different firmwares, and also tried TWRP 2.8.7.0 a few times with different versions of Odin but nothing would work.
I reinstalled the firmware BOJ1, nothing
Tried PIT again, nothing
Then, after trying PIT I got the Firmware error and connected to Kies... It worked, but now I just have a blank screen (another seemingly common issue with these paperweights) - Unsure what to do now, the phone is on, i can call it, find it with device manager but the screen is just blank. FML.
Click to expand...
Click to collapse
OK, so they phone is working, there's just no display...
OK, try resetting the phone remotely from here first
https://www.google.com/android/devicemanager
If it's not connected to the network - try this
http://forums.androidcentral.com/sa...ory-reset-galaxy-s5-computer.html#post4365754
If that still fails, try flashing a stock KitKat ROM from Sammobile, see if downgrading the OS is a big enough change for it to overwrite whatever is causing the problem
Wondering if TWRP has flashed, but the no screen thing is stopping you from knowing one way or another - if we could get into TWRP, we'd have a lot more options, including custom ROMs
---------- Post added at 10:00 ---------- Previous post was at 09:44 ----------
Uploaded the latest KitKat ROM
Code:
https://mega.nz/#!eIQEAQ6a!ztOhVwFuI2MpD6OBhxC-TtgwUJQCxtwnfDQvFOl3g40
*Detection* said:
OK, so they phone is working, there's just no display...
OK, try resetting the phone remotely from here first
https://www.google.com/android/devicemanager
If it's not connected to the network - try this
http://forums.androidcentral.com/sa...ory-reset-galaxy-s5-computer.html#post4365754
If that still fails, try flashing a stock KitKat ROM from Sammobile, see if downgrading the OS is a big enough change for it to overwrite whatever is causing the problem
Wondering if TWRP has flashed, but the no screen thing is stopping you from knowing one way or another - if we could get into TWRP, we'd have a lot more options, including custom ROMs
---------- Post added at 10:00 ---------- Previous post was at 09:44 ----------
Uploaded the latest KitKat ROM
Code:
https://mega.nz/#!eIQEAQ6a!ztOhVwFuI2MpD6OBhxC-TtgwUJQCxtwnfDQvFOl3g40
Click to expand...
Click to collapse
Thanks,
I'll wait for that to download and try.
So - I used accessibility mode to get into settings and do a factory reset... It was difficult, I even thought that the Dark Screen setting might have mysteriously have been turned on but nope.
Rebooted and got the Bootloader screen with the Samsung logo and Recovery Booting text, after a few minutes the screen went blank and the phone vibrated and then nothing!!! :crying::crying::crying:
I have just put it into download mode (I only know this because the many hours I've spent doing this I noticed that the battery and device goes cool when its in download mode) and will try the KitKat flash once its downloaded - Thank you for that btw.
Its so strange - it cant be an issue with the actual screen because it *sometimes* displays the logo.. What can it be?? Its also odd that from when I originally reset it, it could'nt boot into recovery. I'm worried that everything I have done has screwed it up more? Can the Recovery/Bootloader be "Broken"? Its so confusing, I hate tech that doesn't behave.
didscub said:
Thanks,
I'll wait for that to download and try.
So - I used accessibility mode to get into settings and do a factory reset... It was difficult, I even thought that the Dark Screen setting might have mysteriously have been turned on but nope.
Rebooted and got the Bootloader screen with the Samsung logo and Recovery Booting text, after a few minutes the screen went blank and the phone vibrated and then nothing!!! :crying::crying::crying:
I have just put it into download mode (I only know this because the many hours I've spent doing this I noticed that the battery and device goes cool when its in download mode) and will try the KitKat flash once its downloaded - Thank you for that btw.
Its so strange - it cant be an issue with the actual screen because it *sometimes* displays the logo.. What can it be?? Its also odd that from when I originally reset it, it could'nt boot into recovery. I'm worried that everything I have done has screwed it up more? Can the Recovery/Bootloader be "Broken"? Its so confusing, I hate tech that doesn't behave.
Click to expand...
Click to collapse
Does sound like a possible hardware problem, but unlikely or a huge coincidence that it all started after resetting, so I'd be more inclined to think otherwise
Just remembered about this unbrick image / tutorial
http://forum.xda-developers.com/galaxy-s5/general/g900f-debrick-img-lollipop-t3240626
Might be worth giving that a shot
*Detection* said:
Does sound like a possible hardware problem, but unlikely or a huge coincidence that it all started after resetting, so I'd be more inclined to think otherwise
Just remembered about this unbrick image / tutorial
http://forum.xda-developers.com/galaxy-s5/general/g900f-debrick-img-lollipop-t3240626
Might be worth giving that a shot
Click to expand...
Click to collapse
OK - might be a massive chore rooting and installing busybox.. Worth a shot though. Can I not use it with Odin??
didscub said:
OK - might be a massive chore rooting and installing busybox.. Worth a shot though. Can I not use it with Odin??
Click to expand...
Click to collapse
You don't need busybox, that's for creating your own debrick image, the tutorial stops here:
Flash this Debrick file to your 16GB Micro SD card with Win32DiskImager
*Insert your Micro SD card into your computer (backup any information you may have on it we are going to ERASE, FORMAT it to ex FAT
*Open win32DiskImager
*Navigate to the location where you downloaded the correct Debrick file
*Select your Debrick file by double clicking on it
*In the upper right corner of Win32DiskImager you should make sure that the drive letter assigned to your sd card is selected.
***Which ever drive that is listed will be erased, formatted
*Click write in the bottom right hand side
put the Debrick SD card in the Phone, Pull and Replace the Battery
Plug phone in usb and boot into download mode
yout phone should boot into download mode then flash stock firmware via odin
Download link : https://drive.google.com/file/d/0ByA...ew?usp=sharing
You're saying you can't see anything on screen in download mode, just guessing it's there because it cools down - but that could also mean it's not in any mode
With this method, you might get a display to use, then you can flash normally with ODIN with download mode visible on screen
Help: G4 Plus won't start after accidentally hitting "Open" on icon pack install.
I got this phone literally yesterday, it's unrooted, worked perfectly fine until my hand slipped when installing an icon pack from the play store and I hit "Open" - the phone immediately crashed, and now will not boot. I've tried using standard power on, powering on through the recovery bootloader, and entering recovery mode through said bootloader, in every instance it displays the Motorola startup screen, plays through its sequence of animations, then as soon as the Lenovo brand icon shows on screen emits one long pulse of vibrate and then turns off again.
I can't pull the battery because I don't have the required micro-hex screwdriver. Can anyone help?
Yodhrin said:
I got this phone literally yesterday, it's unrooted, worked perfectly fine until my hand slipped when installing an icon pack from the play store and I hit "Open" - the phone immediately crashed, and now will not boot. I've tried using standard power on, powering on through the recovery bootloader, and entering recovery mode through said bootloader, in every instance it displays the Motorola startup screen, plays through its sequence of animations, then as soon as the Lenovo brand icon shows on screen emits one long pulse of vibrate and then turns off again.
I can't pull the battery because I don't have the required micro-hex screwdriver. Can anyone help?
Click to expand...
Click to collapse
can you reboot to bootloader and start recovery? Then clear cache and see if it helps to boot your device? Or if not make a factory reset if it won't help. Maybe the icon pack screwed up something.
Report back. After that, if nothing worked, you can try this:
Is your device recognized by fastboot? If yes, try "fastboot devices" and see if it shows serial number.
Then try to flash the latest stock in the following guide rom if you have one of this devices https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
strongst said:
can you reboot to bootloader and start recovery? Then clear cache and see if it helps to boot your device? Or if not make a factory reset if it won't help. Maybe the icon pack screwed up something.
Report back. After that, if nothing worked, you can try this:
Is your device recognized by fastboot? If yes, try "fastboot devices" and see if it shows serial number.
Then try to flash the latest stock in the following guide rom if you have one of this devices https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
Hi, thanks for responding. After four or five attempts to boot into recovery it succeeded; wiping the cache did nothing so I did a factory reset, which worked and now the phone will boot to the setup stage. Unfortunately now I'm getting "The device was reset. To continue, sign in with a Google Account that was previously synced on this device.", which after googling seems to be a security feature - the problem is it doesn't accept the google account credentials, every time I enter them it just cycles back to the "This device was reset..." screen again.
I know I'm not getting the details wrong since I made the account specifically for the phone and have the details written down. Any suggestions on how to proceed?
EDIT: Actually nevermind, I managed to follow along with a tutorial on how to bypass it using MotoService & ADB. Thanks again for replying.