I was trying to install a rom, for the first time. everything went smooth, progress bar hit 100% and the phone reset. "Touch pro" came up, sits there for about 1 minute then the phone restarts...it keeps doing this in a loop.
what can I do?
Hi,
buffalolsx said:
I was trying to install a rom, for the first time. everything went smooth, progress bar hit 100% and the phone reset. "Touch pro" came up, sits there for about 1 minute then the phone restarts...it keeps doing this in a loop.
what can I do?
Click to expand...
Click to collapse
I guess you've done anything wrong, i guess it's a missing HardSPL
To fix it, get the official ROM for exact your branded device, your language and so, then
go into bootloader mode, connect to your pc, start the upgrade, then your device should work again.
--------
If you want to flash a custom made rom in the future, you have to install the proper HardSPL first (!),
HTH
Related
My TP2 (Sprint) battery went too low and turned off. After charging the battery, the phone just comes up to the Sprint splash screen (Yellow Sprint Symbol) and gives a little vibrate and reboots again. This goes on continuously till I pull the battery . I on am Stock Sprint WM6.1
I can enter into the bootloader screen. I have tried
1. Task 29s
2. Flashed a different radio.
3. Reflashed Stock 6.1 ROM again.
4. Hard Reset it a couple of times
My phone is HSPL unlocked in that I see *olinex 1.0 when I go into the bootloader.
I have tried flasing ROMS from both the SD card as well as from the PC. I cannot go past the green Win 6.1 screen .
I am out of ideas and would really appreciate it if anyone saw this signature previously or has any ideas as to how to solve this.
TIA
baikal2 said:
My TP2 (Sprint) battery went too low and turned off. After charging the battery, the phone just comes up to the Sprint splash screen (Yellow Sprint Symbol) and gives a little vibrate and reboots again. This goes on continuously till I pull the battery . I on am Stock Sprint WM6.1
I can enter into the bootloader screen. I have tried
1. Task 29s
2. Flashed a different radio.
3. Reflashed Stock 6.1 ROM again.
4. Hard Reset it a couple of times
My phone is HSPL unlocked in that I see *olinex 1.0 when I go into the bootloader.
I have tried flasing ROMS from both the SD card as well as from the PC. I cannot go past the green Win 6.1 screen .
I am out of ideas and would really appreciate it if anyone saw this signature previously or has any ideas as to how to solve this.
TIA
Click to expand...
Click to collapse
You could try re-locking the phone, installing the stock 6.5 rom, and then unlocking the phone again.
Also be sure to give it lots of time during the first boot (like do the install, and then leave to make dinner or something). There have been days where I though the phone had locked up, only to have it finish booting when I was about to pull the battery.
wizardknight said:
You could try re-locking the phone, installing the stock 6.5 rom, and then unlocking the phone again.
Also be sure to give it lots of time during the first boot (like do the install, and then leave to make dinner or something). There have been days where I though the phone had locked up, only to have it finish booting when I was about to pull the battery.
Click to expand...
Click to collapse
Wizard,
I ma noob and was wondering the need for relocking. Does it have any benefits as opposed to simply flashing WM 6.5 on to the phone. I have flashed WM 6.5 onto the phone and it goes all the way to the Orange screen(Preparing for activation or something like that with the progress bar) and then reboots again endlessly.
My hesitancy with re-locking comes from the fact that to unlock you need to be in a position to active sync and if the flash fails after the relock ,I might not be in a position to unlock again.
baikal2 said:
Wizard,
I ma noob and was wondering the need for relocking. Does it have any benefits as opposed to simply flashing WM 6.5 on to the phone. I have flashed WM 6.5 onto the phone and it goes all the way to the Orange screen(Preparing for activation or something like that with the progress bar) and then reboots again endlessly.
Click to expand...
Click to collapse
In rare cases re-locking and then re-unlocking resolves rom loading issues.
baikal2 said:
My hesitancy with re-locking comes from the fact that to unlock you need to be in a position to active sync and if the flash fails after the relock ,I might not be in a position to unlock again.
Click to expand...
Click to collapse
As your phone does not boot, I don't see why you are worried about it. You have nothing to lose. Your phone does not work now at all.
You can always flash a stock rom to a locked phone anyway. The only tool that would rule out is the task 29, and you already said that didn't work.
Either way I would try to load the stock wm 6.5 rom, and give it a very long time to finish loading before doing anything else first.
I have to echo WizardKnight's advice here... It seems crazy, but it fixed one of my dead TP2's. It wouldn't boot past the first white HTC screen, I never even got the OS screens to load...
I tried literally everything I could think of... for some reason relocking it revived it...
So ive been running CM 10.1 with CWM v6.0.4.3 for several months without major issue until last night. I went to send a text message to someone, and right as i went back to my home screen, the phone froze, rebooted, and when it finished rebooting, the deice would freeze again as soon as the lock screen was reached, and reboot again. Cue repeated circle of freeze, reboot, finish rebooting, freeze, reboot.
I turned the phone off by taking out the battery, put it back in and charged it overnight without booting it up. Went to start the phone today, same issue still. I would boot into recovery and try to re-flash the OS, and it would give me a status 7 error. After re-downloading everything into my sd card, i was eventually able to get the system to re-install cm10.1.3, and it booted up normally. I downloaded and installed ROM Manager, and installed the newest version of CWM Touch, version 6.0.4.5, and then tried to boot into recovery to install CM11. It showed the CWM Hat icon in the middle of the screen, with the version on the bottom of the screen, then rebooted on its own without showing any menu options.
Now if i try to boot into recovery, it just shows the icon and version again, then reboots, and wont go past the CM loading screen with the spinning cyanogenmod icon.
Not sure what to do at this point, i cant get into recovery to try and flash something new, and i cant get past the CM loading screen to actually use my phone. Any ideas? I have zero experience with adb, so im stumped.
UPDATE: Solved, i flashed TWRP over CWM using Odin, and was from there able to re-install the OS. Things seem to be working fine for the most part, with the exception of one random reboot last night.
Salomon3068 said:
So ive been running CM 10.1 with CWM v6.0.4.3 for several months without major issue until last night. I went to send a text message to someone, and right as i went back to my home screen, the phone froze, rebooted, and when it finished rebooting, the deice would freeze again as soon as the lock screen was reached, and reboot again. Cue repeated circle of freeze, reboot, finish rebooting, freeze, reboot.
I turned the phone off by taking out the battery, put it back in and charged it overnight without booting it up. Went to start the phone today, same issue still. I would boot into recovery and try to re-flash the OS, and it would give me a status 7 error. After re-downloading everything into my sd card, i was eventually able to get the system to re-install cm10.1.3, and it booted up normally. I downloaded and installed ROM Manager, and installed the newest version of CWM Touch, version 6.0.4.5, and then tried to boot into recovery to install CM11. It showed the CWM Hat icon in the middle of the screen, with the version on the bottom of the screen, then rebooted on its own without showing any menu options.
Now if i try to boot into recovery, it just shows the icon and version again, then reboots, and wont go past the CM loading screen with the spinning cyanogenmod icon.
Not sure what to do at this point, i cant get into recovery to try and flash something new, and i cant get past the CM loading screen to actually use my phone. Any ideas? I have zero experience with adb, so im stumped.
Click to expand...
Click to collapse
You can try to reflash CWM with Odin, if that not working, you could try to Odin back to stock.
buhohitr said:
You can try to reflash CWM with Odin, if that not working, you could try to Odin back to stock.
Click to expand...
Click to collapse
I figured it out yesterday actually and forgot to update! Indeed I was able to flash TWRP with odin, since CWM seemed to be blocking me from doing anything. Once that was up and running, things went back to normal, i was able to flash CM 10.2.1 and things seem to be working now.
One thing though, while playing skyrim last night i had it on the charger next to me, and the phone randomly rebooted without any interaction from me. Was odd, but it hasnt done it since. Keeping an eye on it still.
I ended up sending this to Samsung for repair. Luckily my tab was still under warranty. It took them 3 times to finally get it fixed correctly. First time they replaced the main board and the data link cable plug. When I got it back it lasted about an hour before it started doing the reboot loop again. So I sent it back and that time that did a software upgrade, but they obviously didn't even test it before sending it back cuz it only lasted 30 min. then it started with the reboot loop. Before I sent it back for the 3rd time I got in contact with a manager cuz I was so frustrated at this point. That time I sent the tablet directly to her to make sure it was fixed and tested before sending it back to me. I've had it for about 2 weeks now with no problems. They replaced the main board again. So either they gave me a faulty one the first time they "fixed" it or they didn't do anything to it.
So if your tab is stuck in the reboot loop and there's nothing you can do to make it stop, contact Samsung.
I bought this about 2 weeks ago and got to use it for about 5 days.
Woke up in the middle of the night cuz I kept hearing the start up sound to my tablet. So what it does is starts up then I get a prompt saying "Unfortunately, the process com.google.process.gapps has stopped" I click ok and then another prompt that says "Unfortunately, Goole+ has stopped" with the choice of clicking "Report" of "Ok" then the screen freezes and it all starts again.
So I have about 3 - 5 seconds after it starts up and I've tried going in and doing a system restore but it crashes before I can do that. I have manged to go in and delete my google account but when it restarts my account is back.
So then I tried using the Odin3 program with every different file that I could find that would be compatible with my tab and it shows that it installs fine but nothing ever changes on the tab it self. I have tried using the Pit file and the stock rom, the stock rom alone, the pit file alone, twrp open recovery, clockwork open recovery, CF Auto Root, but no luck. I have tried having the auto reboot on and off and then rebooting it myself, still no change.
When I go into recovery mode it shows the android with a red triangle. and of course if I try to install anything from there it always does the signature fail. Which I'm guessing cuz it's not rooted. So at this point I am wondering is there a way to just completely wipe everything off and start completely over? I have wasted so much time on this POS I'm about to just throw it away. Any advice would be more greatly appreciated.
Thank you.
GT-P5100
Hi Im a new member. Im have the same trouble also.
there is an endless restart cycle, and my tablet can last only for around 10 to 15 seconds power on then it will restart again and repeat the process until the battery die.
I can only power off if i connect to the power supply.
I already tried ODIN with several stock PDA files, root with CWM and philtouch, but nothing happens. Everything is passed but there is no change on the about devices after the reboot. Then it continue the endless restart again.
When i boot in original recovery, there is an error already. if i flash zip file root, there is an error in signature.
Please help me brothers and sisters.
Any luck figuring this problem out?
OSANG said:
Hi Im a new member. Im have the same trouble also.
there is an endless restart cycle, and my tablet can last only for around 10 to 15 seconds power on then it will restart again and repeat the process until the battery die.
I can only power off if i connect to the power supply.
I already tried ODIN with several stock PDA files, root with CWM and philtouch, but nothing happens. Everything is passed but there is no change on the about devices after the reboot. Then it continue the endless restart again.
When i boot in original recovery, there is an error already. if i flash zip file root, there is an error in signature.
Please help me brothers and sisters.
Click to expand...
Click to collapse
Have you had any luck fixing this problem?
OSANG said:
Hi Im a new member. Im have the same trouble also.
there is an endless restart cycle, and my tablet can last only for around 10 to 15 seconds power on then it will restart again and repeat the process until the battery die.
I can only power off if i connect to the power supply.
I already tried ODIN with several stock PDA files, root with CWM and philtouch, but nothing happens. Everything is passed but there is no change on the about devices after the reboot. Then it continue the endless restart again.
When i boot in original recovery, there is an error already. if i flash zip file root, there is an error in signature.
Please help me brothers and sisters.
Click to expand...
Click to collapse
Same Problem with me, for me it says USB device is not recognized and I cannot sent anything from my computer now. Totally Stuck with this stupid thing.
My Karbonn Sparkle V appears to have bricked itself, I don't know why, I don't know how to fix it, and I don't have the money or time to replace it. I turned it off when I was going to a job interview, prior to which it was working fine. Afterwards I tried to turn it back on, and for the last 12 hours I've been fighting to get it working again with no success.
I can get into recovery mode, but nothing more. If allowed to try a normal boot, then it will either stay on the "Karbonn Smart" logo screen forever and ever amen, or it will APPEAR to boot, but once it reaches the lock screen it dies on its arse. The best-case is that the lock screen will stay up for about 3 seconds, then the screen will go black for another 3 seconds, and then we go back to the lock screen and the process repeats. OR, the lock screen comes up, 3 seconds, and then we go back to the bouncing dots loading screen forever and ever amen.
I tried a hard wipe from recovery mode - it's made absolutely no difference.
This is a stock phone which has only ever received the OTA updates; I've never rooted it, I don't have a custom recovery installed, and I've never used ADB before today.
I've downloaded a number of "stock ROMs" for this phone, but none of them actually work for me; it doesn't seem to matter whether I try to install them through Recovery mode\Apply update from ADB, or put them on the SD card and try "Apply update from SD card". For most of them, I get the error "failed to verify whole-file signature" and it won't install; I tried to install the stock file from https://forum.xda-developers.com/crossdevice-dev/android-one-general/ota-links-t3287707 but that doesn't get me much further; The error becomes
"Package expects build thumbprint of 6.0.1/MMB290/2459718:user/release-keys or 6.0.1/MMB29K/2419427:user/release-keys; the device has 6.0.1/MOB31E/3142026:user/release-keys"
Click to expand...
Click to collapse
I have pretty much no idea what I'm doing here; Please help.
Hi all, have a rooted OPO that was running ExodusOS. I decided to try a flash of Lineage and so booted into recovery, backed everything up, flashed it. Everything seemed to go okay but after the boot logo the screen just goes black and stays that way until it gets shut back off. I went back to TWRP, loaded my backup and all seemed well as I was still able to use my old backup just as normal. Well, I tried reflashing Lineage from TWRP again and I still get the same black screen issue. This time, however, the phone will neither boot into Fastboot nor into recovery mode and just goes straight into loading Lineage. Because of this I am left with a soft brick until I can get this straightened out. I tried connecting the phone to my PC but it is not detected as a device. I only need to boot into my backup one more time so that I can back everything up, so even if it's only a temporary fix, I'm okay with that too. Any suggestions?
AMpageg2 said:
Hi all, have a rooted OPO that was running ExodusOS. I decided to try a flash of Lineage and so booted into recovery, backed everything up, flashed it. Everything seemed to go okay but after the boot logo the screen just goes black and stays that way until it gets shut back off. I went back to TWRP, loaded my backup and all seemed well as I was still able to use my old backup just as normal. Well, I tried reflashing Lineage from TWRP again and I still get the same black screen issue. This time, however, the phone will neither boot into Fastboot nor into recovery mode and just goes straight into loading Lineage. Because of this I am left with a soft brick until I can get this straightened out. I tried connecting the phone to my PC but it is not detected as a device. I only need to boot into my backup one more time so that I can back everything up, so even if it's only a temporary fix, I'm okay with that too. Any suggestions?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Sounds like a Hardware issue? Sorry to say what your saying doesn't add up and or make sense. Fastboot should work no matter what even if you soft brick it and mess up recovery. I suggest letting the power fully drain maybe and google how to fast boot in case you are doing it wrong.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Click to expand...
Click to collapse
I've tried that but it can't find the phone. The phone gets detected as a new device in windows as evident from the device connection sound but it also never shows up in the list of devices from My Computer.
AMpageg2 said:
I've tried that but it can't find the phone. The phone gets detected as a new device in windows as evident from the device connection sound but it also never shows up in the list of devices from My Computer.
Click to expand...
Click to collapse
I agree with what @Shinobi_warrior said.Seems like you just have a soft brick,so you should be able to boot into fastboot mode without any issues.Are you sure you're doing it the right way? Did you try draining battery completely and then booting into fastboot(yes,you don't need much battery to boot into fastboot mode)?
Well I was finally able to get the device detected by ADB, but it just shows as offline. I attempted to use the repair kit and nothing seemed to happen. I also attempted a different tool (https://forum.xda-developers.com/on.../oneplus-one-toolkit-manudroid19-gui-t2807418) and then booting into either fastboot or recovery that way, a terminal window pops up and quickly disappears, and then nothing else happens. I still see the TugaPower boot logo and it still goes to the blank black screen after this.