Related
Okay, I've searched and searched and no one seems to have the specific problem that I'm having with my phone, so I'm taking to the forums myself. I've been rooting since the G1, I know how to adb push things, I have used google and multiple forums to try to fix this problem. So here goes, anyone that can help I thank you in advance.
1-My phone, like some other MT4G users, reboots itself each time it's plugged in. Initially I thought this was because I was using a Kindle cord to plug it into the pc, so I bought an MT4G usb cable from tmobile, and still it boot loops (just the first white screen for maybe 4 seconds, then black then again and again). The only way to charge it is to let it start boot looping, take the battery out, turn it on, and if I'm lucky enough that it begins to boot up correctly I plug it in mid boot. If I wait til it's fulled loaded it just starts rebooting again.
2-It will not at all from any angle go into Recovery mode. If I try to go to recovery from Rom Manager, or from the screen you get when holding power and lower volume key or by flashing a rom through Rom Manager, it just boot loops just like mentioned above, until I pull the battery for a while (it is currently sitting next to me with the battery out) and then put it back in.
3-If by chance it's on, and plugged into the computer, it is not at all recognized. Ever. While it's booting up my computer finds something, but doesn't know what it is, and doesn't allow me to view any folders on the SD card. Yes I've installed the HTC drivers file. I've adb'ed things to this phone before, now it says device not found. I don't know when it stopped being recognized...
4-I've even tried to fastboot something over to it, but to no avail, still not found.
If I try to do a factory reset, it boot loops. If I sneeze it boot loops.... I don't know what to do, and if I trade it in under warranty, I have to reset it to stock rom, or they're going to charge me for a new phone. Any ideas!?
I have Cyanogen mod 7 on here.
have you tried a fastboot wipe? or have you tried to reboot to recovery from adb?
First, I don't trust using the actual ROM Manager app to do the flashing/installing.
Since you've been flashing since the G1 days why not use Clockwork Recovery? Just go into recovery and do the necessary wipes.
So I suggest to do a complete full wipe in Clockwork, meaning wipe data, cache, and dalvik cache. Install the newest CM nightly (Which is working wonderfully BTW) and see if your problems still persists.
Edit: I didn't realize you tried to enter recovery, oops. But yeah try what the buy above me said. Try re-installing the latest CWM recovery, if that still fails then try heading into there via ADB.
mackster248 said:
First, I don't trust using the actual ROM Manager app to do the flashing/installing.
Since you've been flashing since the G1 days why not use Clockwork Recovery? Just go into recovery and do the necessary wipes.
So I suggest to do a complete full wipe in Clockwork, meaning wipe data, cache, and dalvik cache. Install the newest CM nightly (Which is working wonderfully BTW) and see if your problems still persists.
Click to expand...
Click to collapse
I second that, flashing ROMs from ROM Manager a terrible idea.
Well...if all else fails and if you are really thinking about returning it and still under warranty...few seconds in the microwave method should work just fine. They wont be able to see that its rooted if the phone wouldn't turn on, would they???
glimmer of hope...
So by the grace of god I did get it flashed back to unrooted, stock 2.2 by putting it as pd15img.zip on my sd card and going into bootloader. Once that was done I thought I would be out of the woods... I even plugged it in last night and no boot loop!! but this morning I unpllugged it (and I'm using a tmobile cable for the phone attached to my pc) and here it sits, next to me again with the battery out of it because everytime I try to turn it on (for over 40 minutes now) it boot loops to that stupid white screen (that is honestly driving me insane at this point). I know that it isn't rooted (because I dl'ed rom manager and it won't let me do anything without being rooted) so do we think that I'm safe to go to the store today to request a new one be sent? Thoughts? And thanks for the help thus far!
yeah I would send that back
Bad emmc chip? I'm sorry man, that's a terrible story.
Sent from my HTC Glacier using XDA App
I've been a stalker on here for a long time, as I've been interested in custom ROMs but I never pulled the trigger, until last night. My Vibrant has served me well for a many years, I bought it shortly after they came out. All I'd ever done to it was network unlock it so I could keep using it after I moved to the UK.
I've been toying with getting a new phone for a few months now so I decided why not try and flash a custom ROM and get ICS on my Vibrant, if I got the EU error and bricked it, oh well, I'd get a new phone. So I after much reading and research, studying the tutorials on here I went for it. I am vary tech and computer savvy. I build my own computers from scratch, I've flashed my routers and set up networks so I was pretty confident I could do this with the help of the forums here.
I've read every thread I can find on the EU on here and I know that the community needs as much info as possible to try and solve this bug, so I will try and be as specific as possible and list everything I did. But bear in mind, I'm new to this and this was my first time doing much of this so some things may be muddled as I was up til quite late messing with all this.
To start my phone was running 2.2 which was updated using Kies Mini. The only thing I'd ever done to it was network unlock, and for that all I did was find the file on the phone with the code and then enter it to unlock.
I decided to follow Woodrube's guide (http://forum.xda-developers.com/showthread.php?t=1464423)
I followed the guide to the "T".
1. Used Odin to flash back to stock 2.1, worked fine, phone booted back up and everything worked. Phone Data showed I was on 2.1.
2. I put Clockwork Recovery downloaded from Woodrube's sig block on my internal sdcard labeled as Update.zip
3. Created a folder called ICS on my internal sdcard. Found and downloaded CM7 from the forums here and dropped it into the ICS folder. Found and downloaded the ICS Passion ROM from the forums and dropped it into the ICS folder
4. Booted to recovery mode and did Reinstall Packages. It ran but brought me back to the blue recovery screen. so per Woodrube's guide I did it again and the second time it brought me to the green CWR recovery screen
5. I did wipe data/ factory reset
6. I did wipe cache
7. I went to advanced and did wipe dalvik cache
8. I went to mounts and storage and did format system
9. I went to install from sdcard and found the ICS folder I made and ran the CM7 fille I dropped there. It worked the first time and booted right up, I let it sit for about 5 mins waiting for the request to install my google password as Woodrube mentions, but it never appeared, so I moved on after 5-6 min of waiting.
10. I then booted back into recovery mode using the extended power button menu
11. I went to install from sdcard again and this time ran the ICS Passion file. It ran some text lines showed on the screen as id did somethings and then I sw a Random Offset error and a small hex string but then it said successfully installed but didn't leave the recovery screen. So i scrolled up to reboot system.
12. The phone rebooted, showed me the Passion splash screens and a progress bar which filled and completed, then showed a few other splash screens and then it booted up showing my signal strength bar and notifications bar. I thought YES! I did it and it worked. then the screen flashed, it showed a single multi-colored line horizontally across the middle of the screen and then flashed again and I was looking at the Encryption Unsuccessful screen.
13. I DID NOT PUSH THE RESET BUTTON, I set the phone aside and followed Woodrube's link to the Captivate Forums and read up on the error, read all of it, then searched the forums for more threads on the error and read all of those, then I Googled the error and read everything else I could find.
14. First i tried just shutting the phone down with the power button and then restarting it. I did this about 5-6 times. Every time it rebooted it showed me the Passion splash screens then boots up shows my notification bar and signal strength meter and the EU screen. That didn't work. I next tried rebooting 5 times without my external sd card installed. Same results
15. Next I decided to see if I had lost access to my internal sdcard as I had read about. I wasn't sure if I had because I had never pushed the EU screen reset button. So I booted into recovery mode, went to install from sdcard and my sdcard list popped up. I still had access to my internal sdcard.
At this point I was torn... do I stop playing with fire and just got back to stock, update with Kies Mini and go back to using the phone as I had always been and forget all this or do I try and figure this out? Well my stubborn side hating to be stumped had encountered a problem and so wanted to move forward... on i went.
16. I decided, ok, I can still see my internal sdcard so why not try reflashing the ISC Passion and see if maybe it will take this time with no EU. I ran it and exactly the same thing happened as the first time.. right down to the flash with the horizontal line and all. (I did not wipe data, cache or anything, just reflashed. Not sure if I should have or not)
17. Back to recovery mode and check... yes still see my internal sdcard. hmmm
18. Decide ok, how about it I do Woodrube's guide all over again from the start? Maybe that will work. I followed the guide again using all the same files and wound up right back at the EU screen again.
19. Hmmm, how about a different ICS ROM? Went and found ICZen and downloaded it. Hmm, how do I get this unto my internal sdcard if the phone won't boot all the way? Booted it back to the EU screen and just plugged the phone into the usb on my computer, windows recognized it, made the device plugged in noise, and both my internal and external sdcards on the phone showed up as drives. Navigated to the ICS folder in the internal sdcard and dropped the ICZen file into it.
20. Rebooted the phone into recovery mode using the power button menu
21. Used install from sdcard and flashed the ICZen. (Again, I didn't wipe anything before hand. Again not sure if I was supposed to)
22. The ROM installed and got stuck in a boot loop. I pulled the battery and rebooted to recovery and reflashed the ICZen again with no wipes. This time it worked and the phone rebooted and I got the ICZen splash screens, then the notification bar and signal strength meter showed up.. and AGAIN the weird flash with the horizontal bar and then the EU screen. SIGH
23. Booted back to recovery mode and checked if I still had access to internal sdcard. yes it was still there.
24. Shut down and booted to download mode and ran Odin and flashed back to stock 2.1
This is where I am now, It was too late to try anything else and my wife was glaring at me to go to bed so shut off the phone and went to bed.
I tried to put everything I did down with as much detail as I could. I'm sure some of you pros out there might be wincing at stuff I did, but again this is all new stuff for me and I'm slowly learning.
If you have any questions or need clarification just ask and I will try and help/explain better.
Hopefully this might help in the quest to solve this bug or it may just be a waste of time to read, dunno.
I got to:
"To start my phone was running 2.2 which was updated using Kies Mini."
and stopped there
Come back to Froyo - always welcome here
Moped_Ryder said:
I got to:
"To start my phone was running 2.2 which was updated using Kies Mini."
and stopped there
Come back to Froyo - always welcome here
Click to expand...
Click to collapse
LOL, yea I know, but up until this adventure last night, I just used the phone with the Samsung updates as it was, didn't really have a need to do otherwise.
I think that you should flash one of Moped's ROMs and make sure that it will boot up and run ok and that you did, in fact get out of the EU bug safely.
Couple of things:
I did get your PM and I thank you for the info. This post is far more detailed, which is a ton better.
You say that you were unlocked. There was a theory not too long ago about a corrupted EFS file, but AdamOutler uploaded his and someone else replaced theirs with it and it didn't work. But I am thinking that there might be a link here bc I have seen several posts over the last few months that ICS ROMs have been out where someone's data has been borked or their IMIE was gone. Wonder if there is a correlation to that? I'll have to ask some people onver in the Captivate thread and if anyone in the Vibrant thread can chime in too(?).
If you want to flash another ROM, just follw my ICS guide but where it says to install CM7, just install your shiny, new 2.2 instead and there you are.
Great Job dodging that bullet and hope that you no longer lurk, but be a part of the community at large. If your intelligence is reflected in your post, you are welcome here anytime.
Thanks Woodrube,
I was thinking the same thing about loading a 2.2 ROM and be sure I'm all good.
I know the 2.1 I loaded last thing last night seemed to work fine. But I will try a 2.2 once I get home and will update on here after I do.
Funny thing about all this is that my wife now won't let me near her Captivate ROFL.
Can you blame her ?
For the sake of the thread i can chime in on the unlock part. I'm still untouched by the EU bug "touching wood(rube)" . I'm using the i896 version of the Captivate from Rogers and there was never codes inside of it so most app were unsuccesfull at pulling them. I had to use the free SGS Unlock website where you upload your nv_data.bin and it returns you a unlocked version. I also never encountered any efs/imei issue.
hi.
I saw you have not wiped when installing the ROMs. I think maybe you should try and do the wipe before installing the ICS ROM.
Wipe system, data, cache.
Good luck
romitkin said:
hi.
I saw you have not wiped when installing the ROMs. I think maybe you should try and do the wipe before installing the ICS ROM.
Wipe system, data, cache.
Good luck
Click to expand...
Click to collapse
BINGO!
So I followed Woodrube's guide again.. started from scratch... only change I made was I wiped data factory reset, wiped cache, wiped Dalvik cache, and under mounts and storage I format system BEFORE flashing the ICS Passion.
Logged into Google Account and set up phone and now I'm rockin' ICS
Not sure how or why this worked but it did.
Thoughts?
First time flashing CM, and I may have messed up.
I rooted, installed TWRP, everything went perfect. I made a backup, and then tried to do a factory wipe. The wipe ended with the messages "unable to mount /system", "... /cache" and another one. I still tried to flash, and it just immediately got stuck, nothing happened. I rebooted, and everything worked fine. It was the Samsung stock image and all my apps were still there. I'm assuming it just didn't wipe at all.
I then went full retard mode, and tried to do a restore. I wanted to be sure my phone wouldn't fail on me in the recent future because some random stuff may have been partially wiped or something. Feel free to tell me I have the IQ of a chimp.
This completely messed things up, as it just got stuck at "Restoring System...". Eventually I restarted it with the power button. Now it can't boot normally, it can't boot into recovery mode, which just leaves download mode.
Any way I can fix this and subsequently install CM properly? I'm using TWRP 2.6.3.0. I've been told it's recommended to use 2.5, as the other version may have some issues (including not being able to recognize partitions). Only download mode still seems to work, so maybe there's a way to flash my phone back into the living world?
Versions:
Team Win Recovery Project 2.6.3.0
CyanogenMod 10.1.3 (RC2 jfltexx)
Thanks!
No idea really but maybe try to flash default rom/recovery etc with odin?
I've had this problem. Seeing as you only have download mode you have to flash a stock Rom and start again. Recoveries for our phone are still I development. Use official CMW to install CM, using links in Op.
Sent from my GT-I9505 using XDA Premium 4 mobile app
HANDSY said:
I've had this problem. Seeing as you only have download mode you have to flash a stock Rom and start again. Recoveries for our phone are still I development. Use official CMW to install CM, using links in Op.
Click to expand...
Click to collapse
I got the Samsung stock ROM of july, flashed it using download mode, and everything was back! I then rooted it again, and installed CMW (see versions below). I went into recovery, and tried to do a backup. It told me it failed: "Error while making a backup image of /data!". I then wondered if it may have been due to a lack of storage (which could very well be, as that was the issue before and the old backup by Teamwin was probably still on it somewhere), so I rebooted my phone. That's when it just failed and kept showing the Samsung logo at boot. I tried flashing my ROM again, again the logo. Then I did a factory reset using the regular recovery (cache and data reset), which fixed it. Now all my apps and data are gone, but that's no problem.
I'm back at the unrooted Samsung stock image now. Any ideas what I did wrong? These were the versions I used:
CF-Auto-Root-jflte-jfltexx-gti9505
i9505-cwm-recovery-6.0.3.2(0611)
Odin3 v3.07
I did nothing more than root, install CMW, try a backup and then it all went to ****. I'm surprised a backup can even do that.
Mmm I'm not too familiar with the internal workings of backups. Perhaps something was corrupted during flashing? Glad to hear that you have got your phone working again. There is an updated version of CMW somewhere in the original development thread.
Sent from my GT-I9505 using XDA Premium 4 mobile app
i've had the exact same issue.
I did go back to stock firmware and recovery, rerooted(chainfire) and installed the latest CWM 6.0.3.6.
Then, i did download Jamals Google play 4.3 rom, placed it on my SDcard and did follow the instructions. Works like a charm, and i've got noe clue what happened to my phone. however, it works now.
Chillzone said:
i've had the exact same issue.
I did go back to stock firmware and recovery, rerooted(chainfire) and installed the latest CWM 6.0.3.6.
Then, i did download Jamals Google play 4.3 rom, placed it on my SDcard and did follow the instructions. Works like a charm, and i've got noe clue what happened to my phone. however, it works now.
Click to expand...
Click to collapse
I tried CMW 6.0.3.6 and the Google Play 4.3 ROM as you said, and it works perfectly! I didn't try a backup this time, as it didn't exactly have anything to back up anymore.
Finally my precious vanilla Android again, I missed it since I switched from my Galaxy Nexus to my S4. Thanks a lot guys!
Edit: I do seem to be having one issue. Quite frequently after it's booted, and I enter the SIM pin, the message "Unlocking SIM card..." stays there indefinitely. I can use the phone but the message covers everything up. This doesn't always happen, but quite often. I've read some ROMs can't handle SIM lock, like CM. This is a Google Play edition, however. Is it normal that this doesn't work?
I can seem to fix it by holding the power button, and choosing "Unlock SIM" from the menu. I guess it's not that bad as I don't often reboot my phone.
I've heard ranting and raving about Malladus and I decided to flash it yesterday. It won't take the flash no matter what I do.
I've tried: Flashing 1.2.4, downloading both again to make sure it wasn't a download issue, using different gapps package, using a different lg apps package, using CWM, using TWRP, side-loading... ETC
Bottom line: My phone will not take the ROM. It flashes the LG logo and gets stuck at a black screen where the back-light is on but nothing is displayed on the screen.
I am an experienced flasher and I have no idea what is going on. I am backed up and can get into TWRP to restore so I am all good as far as not being bricked goes but I really want to try out this damn rom.
Any help would be much appreciated. Thanks.
Bump I'm having the same problem, I'm on Verizon.
NBushyy said:
Bump I'm having the same problem, I'm on Verizon.
Click to expand...
Click to collapse
Yeah same here. Verizon. Forgot to mention it.
Still a problem. Bumping.
I am in the boat with you. I thought it was just me.
Same Black Screen issue
Did anyone have any luck resolving this? Ive tried with both twrp and cwm and same issue...?
Same problem on my Verizon model. Using twrp 2.6.3.3. Other roms work fine.
How long have you left it at the black screen? Sometimes a fresh load can take up to 10 minutes.
Also, the rom will work without gapps and lgapps, so try just loading the rom. I know you downloaded twice, but did you check the md5 sum either time?
heleos said:
How long have you left it at the black screen? Sometimes a fresh load can take up to 10 minutes.
Also, the rom will work without gapps and lgapps, so try just loading the rom. I know you downloaded twice, but did you check the md5 sum either time?
Click to expand...
Click to collapse
I left it there for a good 15 minutes. I also had it plugged into my laptop. It kept detecting the phone as plugged in. Seems like it is stuck in a bootloop or something. I also tried installing only the ROM without the gapps and lgapps and had the same result. I also checked the MD5 sum and it matched. (I know I'm kinda hijacking this original post, but I think we are all having the exact same issue)
try this
trackstar1414 said:
I left it there for a good 15 minutes. I also had it plugged into my laptop. It kept detecting the phone as plugged in. Seems like it is stuck in a bootloop or something. I also tried installing only the ROM without the gapps and lgapps and had the same result. I also checked the MD5 sum and it matched. (I know I'm kinda hijacking this original post, but I think we are all having the exact same issue)
Click to expand...
Click to collapse
Can you restore your nandroid and flash say, CleanROM 1.0 or DigitalDream 2.1? OR try this:
1. Hold the power button until the device is OFF.
2. Download LG drivers to the PC (LG VZW_United_WHQL_v2.11.1) and LG mobile support tool (B2CAppSetup).
3. Install these packages.
4. Plug in you USB cable into the phone but not the computer.
5. Hold volume up and insert the USB cable to the PC- the phone should boot to 'download mode'.
6. Open the support tool and click Options>Upgrade Recovery, follow the prompts.
7. At the first prompt indentify your phone using IMEI/ESN, then click OK
8. Let it do its thing, the phone will reboot and most likely have a bunch of error messages and some FC's. Just hit okay to all messages, the phone will settle after 2 minutes or so.
9. Download freegee from market and reflash recovery of your choice.
10. Make sure you have a ROM saved to the SD to flash
11. Use freegee to reboot to recovery
12. Once in recovery you can reflash the ROM as normal.
13. Reboot and Profit!
*$* Or you could go back to Stock and start fresh!
*$* BEFORE ANY FLASH ALWAYS STOP and MAKE A NANDROID BACKUP!
Good Luck and if you get stuck let me know
geosnipe said:
Can you restore your nandroid and flash say, CleanROM 1.0 or DigitalDream 2.1? OR try this:
1. Hold the power button until the device is OFF.
2. Download LG drivers to the PC (LG VZW_United_WHQL_v2.11.1) and LG mobile support tool (B2CAppSetup).
3. Install these packages.
4. Plug in you USB cable into the phone but not the computer.
5. Hold volume up and insert the USB cable to the PC- the phone should boot to 'download mode'.
6. Open the support tool and click Options>Upgrade Recovery, follow the prompts.
7. At the first prompt indentify your phone using IMEI/ESN, then click OK
8. Let it do its thing, the phone will reboot and most likely have a bunch of error messages and some FC's. Just hit okay to all messages, the phone will settle after 2 minutes or so.
9. Download freegee from market and reflash recovery of your choice.
10. Make sure you have a ROM saved to the SD to flash
11. Use freegee to reboot to recovery
12. Once in recovery you can reflash the ROM as normal.
13. Reboot and Profit!
*$* Or you could go back to Stock and start fresh!
*$* BEFORE ANY FLASH ALWAYS STOP and MAKE A NANDROID BACKUP!
Good Luck and if you get stuck let me know
Click to expand...
Click to collapse
I am able to restore my nandroid backup so I'm not completely stuck without a phone. I will try flashing one of the other ROMs and see how it goes now. Thanks for the help so far.
trackstar1414 said:
I am able to restore my nandroid backup so I'm not completely stuck without a phone. I will try flashing one of the other ROMs and see how it goes now. Thanks for the help so far.
Click to expand...
Click to collapse
I was able to install the digital dream rom without any issue. At this point I think its the sequence I did everything. I did the latest ota before installing any Recovery. I used the loki method to install the recovery. In looking at all the roms, it appears that malladus may not be "loki patched" for people already on 12b? Other roms I have tried mention that so thats why I'm speculating this. I am by no means a developer so I might be out in left field on this one. I guess I'll stick with stock or another ROM for now until his next update.
It also looks like people are discussing this on the main ROM forum as well so hopefully it will work in the future.
Thanks again for the help and suggestions.
trackstar1414, say thanks by using the "Thanks' button like this.. keep me informed, CHEERS!
trackstar1414 said:
I was able to install the digital dream rom without any issue. At this point I think its the sequence I did everything. I did the latest ota before installing any Recovery. I used the loki method to install the recovery. In looking at all the roms, it appears that malladus may not be "loki patched" for people already on 12b? Other roms I have tried mention that so thats why I'm speculating this. I am by no means a developer so I might be out in left field on this one. I guess I'll stick with stock or another ROM for now until his next update.
It also looks like people are discussing this on the main ROM forum as well so hopefully it will work in the future.
Thanks again for the help and suggestions.
Click to expand...
Click to collapse
Wanted to share this if you haven't read it..
http://forum.xda-developers.com/showthread.php?t=2449670
I had issues originally and had to flash back to 1.2.3.
What I ended up doing was switching to CWM 6.0.4.4 ( I was using TWRP 2.6.3.3).
His boot skipped the set up wizard as well, which was odd.
His was also the only ROM I ever got stuck on the fastboot screen while using twrp.
Try ( at your own risk obviously) flashing back to an older malladus (wipe all and boot till you get through the set up wizard),
Then back to recovery, do a wipe, without wiping the system partition, Data Cache and Davlik, and flash back to 1.2.5.
I didn't try it on 1.2.5. But that's how I got into 1.2.4.
Srvisg0d said:
I've heard ranting and raving about Malladus and I decided to flash it yesterday. It won't take the flash no matter what I do.
I've tried: Flashing 1.2.4, downloading both again to make sure it wasn't a download issue, using different gapps package, using a different lg apps package, using CWM, using TWRP, side-loading... ETC
Bottom line: My phone will not take the ROM. It flashes the LG logo and gets stuck at a black screen where the back-light is on but nothing is displayed on the screen.
I am an experienced flasher and I have no idea what is going on. I am backed up and can get into TWRP to restore so I am all good as far as not being bricked goes but I really want to try out this damn rom.
Any help would be much appreciated. Thanks.
Click to expand...
Click to collapse
Are you on 12B OTA? If so, that would be your issue. I took the 12B OTA and tried flashing Malladus and got the same issue you have. You can revert your phone to 11A and that should resolve your issue. http://forum.xda-developers.com/showthread.php?t=2448960 it will erase everything on your phone and go back to unroot.
Hi guys!
Yesterday, i used towelroot to root my phone, and installed Safestrap with TWRP as my recovery.
I booted my phone after everything was done, and it worked fine. This is where i screw up... I installed Softkeyz (I thought it might work for the Note 3, but...)
After i installed Softkeyz, and rebooted the phone, my status bar was gone, the background was blue and my task manager didnt work. I went back into the softkeyz app and clicked the "backup" button, wich is said to revert everything back to normal. It didnt.
When i booted my phone after the backup, I still had the same problem.
I then did a Titanium Backup, and went into recovery to factory-reset. it seemed to work, but when my phone boots, I get to the languane selection screen, and then this pops up: "KeyguardTestActivity has stopped". If I click 'OK', the same message pops up and im unable to click "next" or select a language.
I went back into recovey, wiped dalvik, wiped cache, I event formated /data in case there was any virus or anything I had downloaded, did a factory reset, and it stil doesnt work....
I had a ROM on my phone, but it used AROMA so that doesnt work with Safetrap... Now my memory is clean, my phone wont boot, and I cant move any files to the SD-card through regular MTP. I guess I have to use ADB (safetrap can sideload ADB) but I have no idea how to use that, and I have no idea what ROM to use, to get my phone up and running.
I use my phone for work and for studies, and the only reason I wanted to root was for AD-blocker and better batterylife...Now I've messed up..
I've tried searching google and the forums, but cant seem to find any fix. Can anyone out there help me? Please?
EDIT: If i boot the phone WITHOUT the simcard, the error message is gone, but if the screen locks, then in wont unlock. Taskmanager still doesnt work. I managed to get to phone running though, but without taskamanager and a working lock-button.... any help?
EDIT2: after rebooting without the simcard, the same error shows...
ipwngeek said:
Hi guys!
Yesterday, i used towelroot to root my phone, and installed Safestrap with TWRP as my recovery.
I booted my phone after everything was done, and it worked fine. This is where i screw up... I installed Softkeyz (I thought it might work for the Note 3, but...)
After i installed Softkeyz, and rebooted the phone, my status bar was gone, the background was blue and my task manager didnt work. I went back into the softkeyz app and clicked the "backup" button, wich is said to revert everything back to normal. It didnt.
When i booted my phone after the backup, I still had the same problem.
I then did a Titanium Backup, and went into recovery to factory-reset. it seemed to work, but when my phone boots, I get to the languane selection screen, and then this pops up: "KeyguardTestActivity has stopped". If I click 'OK', the same message pops up and im unable to click "next" or select a language.
I went back into recovey, wiped dalvik, wiped cache, I event formated /data in case there was any virus or anything I had downloaded, did a factory reset, and it stil doesnt work....
I had a ROM on my phone, but it used AROMA so that doesnt work with Safetrap... Now my memory is clean, my phone wont boot, and I cant move any files to the SD-card through regular MTP. I guess I have to use ADB (safetrap can sideload ADB) but I have no idea how to use that, and I have no idea what ROM to use, to get my phone up and running.
I use my phone for work and for studies, and the only reason I wanted to root was for AD-blocker and better batterylife...Now I've messed up..
I've tried searching google and the forums, but cant seem to find any fix. Can anyone out there help me? Please?
EDIT: If i boot the phone WITHOUT the simcard, the error message is gone, but if the screen locks, then in wont unlock. Taskmanager still doesnt work. I managed to get to phone running though, but without taskamanager and a working lock-button.... any help?
EDIT2: after rebooting without the simcard, the same error shows...
Click to expand...
Click to collapse
Hello again ok so I don't know a great deal about the note 3 or safestrap. But you have a few options here.
if I'm not mistaken the note 3 takes an external SDcard? can you not copy a compatible Rom using a card reader and install from recovery?
I also believe Fastboot works with note3 but not sure how. you could use this to flash a recovery that will work with the Rom on the phone.
or as drastic measure you could adb pull your data and flash it with Odin. flashing with Odin will wipe everything and return you note3 to out of the box condition.
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Danny201281 said:
Hello again ok so I don't know a great deal about the note 3 or safestrap. But you have a few options here.
if I'm not mistaken the note 3 takes an external SDcard? can you not copy a compatible Rom using a card reader and install from recovery?
I also believe Fastboot works with note3 but not sure how. you could use this to flash a recovery that will work with the Rom on the phone.
or as drastic measure you could adb pull your data and flash it with Odin. flashing with Odin will wipe everything and return you note3 to out of the box condition.
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Click to expand...
Click to collapse
Hey man!
I'm so embarassed I didn't think of the SD card... Now my only problem is that I cant seem to find a ROM that will work... I tried the heisenberg one, but it says "failed" when trying to flash it...
EDIT2: It seems as its my lockscreen that is broken. would that be assosiated with the Kernal? I got a ROM, and it worked, but the same error still occurs..I'm thinking that the Softkeyz-app messed with my kernel, and now killed the phoes lockscreen/kernal. Need a new kernel I guess... but thats messing with something I've never done... any stock kernel?
Danny201281 said:
Hello again ok so I don't know a great deal about the note 3 or safestrap. But you have a few options here.
if I'm not mistaken the note 3 takes an external SDcard? can you not copy a compatible Rom using a card reader and install from recovery?
I also believe Fastboot works with note3 but not sure how. you could use this to flash a recovery that will work with the Rom on the phone.
or as drastic measure you could adb pull your data and flash it with Odin. flashing with Odin will wipe everything and return you note3 to out of the box condition.
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Click to expand...
Click to collapse
Greeeat... I tried flashing the Pacman rom, everything seemed ok, but now i can only boot into the safestrap recovery, and when trying to boot into the system, both with pacman and after trying to wipe everything, it just goes into a black screen...
ipwngeek said:
Greeeat... I tried flashing the Pacman rom, everything seemed ok, but now i can only boot into the safestrap recovery, and when trying to boot into the system, both with pacman and after trying to wipe everything, it just goes into a black screen...
Click to expand...
Click to collapse
sorry dude don't know what to suggest, I don't know safestrap, is it necessary to use or can you use a normal recovery? Safestrap seems very different compared with a normal recovery as it bypasses locked bootloaders and allows for multibooting roms. Are you sure you set it up correctly? Did you make a recovery backup before you started flashing anything?
personally best answer I can give you right now is flash an ruu with Odin to get your phone working, then try rooting again after you've researched it a bit.
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
---------- Post added at 01:22 PM ---------- Previous post was at 01:06 PM ----------
The link below has a list of stock firmware. Find the correct one for your phone model and download it. At the bottom of the page there is also a link to download Odin and the phone drivers if you need them. As long as you can boot to download mode you can unbrick from pritty much anything with this.
http://www.androidrootz.com/p/galaxy-note-3-stock-firmwares.html?m=1
You can also use Odin to root and install CWM recovery. There's a guide in the link below for this
http://wccftech.com/how-to-root-and-install-cwm-on-galaxy-note-3-sm-900/
Good luck man
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Danny201281 said:
sorry dude don't know what to suggest, I don't know safestrap, is it necessary to use or can you use a normal recovery? Safestrap seems very different compared with a normal recovery as it bypasses locked bootloaders and allows for multibooting roms. Are you sure you set it up correctly? Did you make a recovery backup before you started flashing anything?
personally best answer I can give you right now is flash an ruu with Odin to get your phone working, then try rooting again after you've researched it a bit.
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
---------- Post added at 01:22 PM ---------- Previous post was at 01:06 PM ----------
The link below has a list of stock firmware. Find the correct one for your phone model and download it. At the bottom of the page there is also a link to download Odin and the phone drivers if you need them. As long as you can boot to download mode you can unbrick from pritty much anything with this.
http://www.androidrootz.com/p/galaxy-note-3-stock-firmwares.html?m=1
You can also use Odin to root and install CWM recovery. There's a guide in the link below for this
http://wccftech.com/how-to-root-and-install-cwm-on-galaxy-note-3-sm-900/
Good luck man
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Click to expand...
Click to collapse
I'm working on a Odin now... lets hope it works... ghaa...
ipwngeek said:
I'm working on a Odin now... lets hope it works... ghaa...
Click to expand...
Click to collapse
As long as you have correct firmware should be fine, wrong firmware won't flash though so don't panick about that
also make sure you run Odin as administrator and use default options don't tick any boxes manually
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
ipwngeek said:
I'm working on a Odin now... lets hope it works... ghaa...
Click to expand...
Click to collapse
and the verdict?
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Danny201281 said:
and the verdict?
Sent from my HTC One M7 ARHD 71.1 using TapaTalk
Click to expand...
Click to collapse
I'm the worst guy ever,... totally forgot to answer (to be honest, I thought I replied, but my phone didnt actually send the message!)
It worked well! I now just got a LG G3 though, so yaay!