Database Develop

[Q] Stock T-mobile Streak 7 not booting right Please Help!

My streak 7 just started acting up.
1.- I forgot to turn it off and the battery depleted and stayed without charge for about 4 days.
2.- At first it would not boot (after charging overnight) it would get stock on the pink animation.
3.- Contacted tech support and they had me do a factory reset (4 times).
- First time it got stuck on "Formatting DATA" (waited for it overnight)
- All other 3 worked fine.
The problem is that after it boots and I go trough the initial setup (google account, WiFi password - no sim card) it appears to be working properly, except when I turn it off and re-start it ask me for the configuration all over again. Just like if I had done an other system restore. If I try to install something from the market some times the tablet would crash (the screen would blink and then go black) and I have to use the reset pin.
I don't know what to do I'm completely new at this but I'm willing to learn. Any help giving me a direction to go will be greatly appreciated.
Thanks in advance.

You could try to NVflash back to Froyo with this file: http://d-h.st/iXc. What version were you on? This video is the first in a three part series by "giveen" which will show you how to load drivers to NVflash: http://www.youtube.com/watch?v=ydM7qkoCs00. This link will get you all the drivers: http://d-h.st/iqA. The links in the videos no longer work.
This page will get you the latest or last T-Mobile file link: http://forum.xda-developers.com/wiki/Dell_Streak_7#Official.

Thanks !
Thank you for the help. I will be trying this today.

Need more help
I tried doing the restore to factory 2.2 with the instructions above, the flash appeared to finish. But when I restarted the tablet I still have the same problem. Every time I turn it on it acts like it has just been restored to factory defaults.
I tried doing the HoneyStreak flash from here http://forum.xda-developers.com/showthread.php?t=1088225, and I got an error.
Formatting partition 2BCT please wait.. FAILED!
Could this be part of my problem? any other suggestions of what to do.
Thanks for your help.

luis_Hac said:
I tried doing the restore to factory 2.2 with the instructions above, the flash appeared to finish. But when I restarted the tablet I still have the same problem. Every time I turn it on it acts like it has just been restored to factory defaults.
I tried doing the HoneyStreak flash from here http://forum.xda-developers.com/showthread.php?t=1088225, and I got an error.
Formatting partition 2BCT please wait.. FAILED!
Could this be part of my problem? any other suggestions of what to do.
Thanks for your help.
Click to expand...
Click to collapse
You are in read-only status more than likely. Sucks.

OH NOOOOO
Does this mean I'm out of luck and pretty much have a worthless device now?
I've looked up read only mode and no one seams to have a way to get out of it (except for re-soldering components with some expensive machine)
I've also tried the "hold reset pin + capacitive buttons + power button for 2 minutes" with no luck.
And found one that calmed to have fixed it by flashing CWM to it but they did it with a version of CWM for 5.x and up and I'm still in stock 2.2
Please some one tell me there is a solution.

Yup.

[Q] Repair Galaxy Note N7000 SystemUI / TouchWiz home stopped working errors?

Hello everyone,
I've been literally 12 hours searching for possible answers on how to repair my Galaxy Note N7000 which from what I've concluded, has a problem that can be easily repaired but I've found nothing but limitations when I have a go at it. It doesn't seem to be bricked as I can still access recovery mode, download mode and it effectively boots, it's only giving me errors.
Here's what happened:
1) I tried rooting it using UnlockRoot PRO. Paid the PRO version, detected the device. Later I find it says the N7000 with 4.1.2 is not compatible so the rooting process was never completed, so I rooted it using Root_SuperSU.0.95.Only-signed and it worked just fine.
2) Everything worked fine, downloaded Andromizer to customize the phone.
3) Changed the DPI size to test it, then went to Developer Options and changed the Animation scales to 0.5 to make it all run faster.
4) Rebooted the device. Once I did, I got nothing but "SystemUI has stopped working" together with "TouchWiz home has stopped working errors".
I checked around the web and so far, what I've found (and tried) is this:
1) There seems to be a bug related to TouchWiz and the Animation Scale option (or perhaps the DPI size option in Andromizer). So I tried to do a wipe data / factory reset through recovery mode.
2) When trying the wipe data / factory reset through recovery mode, I rebooted the phone, only to find the SAME errors after I registered everything.
3) First option that came to mind was to wipe everything and immediatly reinstall the Official JellyBean 4.1.2 firmware (at this point I want to pretty much unroot the device as I didn't know it was going to give me so much trouble). When I tried that, I realized that SUDDENLY, Odin (nor Heimdall) are NOT detecting the phone in download mode. I'm guessing it's because USB Debugging is turned off but, I can't access the phone settings. It's my only logical conclusion, although it should be turned on given I could install PhilZ Custom Recovery later.
4) I search around the web and it says it's a driver problem. So I uninstall everything, run CCleaner, USBDeview to uninstall everything related to the Samsung Galaxy. Reboot. Install drivers again. Reboot. Plug booted phone and let Windows detect the device, installed successfully. Reboot in download mode. Let windows detect the device, installed successfully. Run Odin: DEVICE NOT DETECTED. (It does detect it while it's booted though, only it doesn't work for **** obviously).
I've literally tried everything. I've tried checking for a way to install the firmware via Recovery Mode instead of Download Mode. I've tried checking for a way to remotely access the device and mod the settings from there using ADB, and I get the same problem in ADB, doesn't detect the device.
Also tried to reset settings to normal via PhilZ Custom Recovery which I managed to install later.
Isn't there just a way to reset all settings to normal? Shouldn't a factory reset do this? How can I get SOMETHING to work and try to recover the phone? Any Aroma Recovery Script? Any way to mess with the system folder and modify settings manually via notepad or something since due to the SystemUI / TouchWiz home errors I can't access the phone settings?
I'm barely awake at this point. Can't believe I've stressed myself this much. Please help. This is beyond retarded.
Thank you,
Z

i had the same exact problem just few hours ago.....first of all you should boot into recovery mood by pressing vol up+ home button+lock button until samsung logo shows and then wipe all data/factory reset and wipe all cache partitions..........if that didnt fix it you should try rerooting it againg after re wiping

I read the post but it seems you have done a lot of things and nothing worked. So what is the situation right now? You can boot as normal but cannot get any icons or settings as sysUI and TW crashes?

Try installing GB ROM then wipe/cache first. If good, root GB ROM then do full wipe. Then test ROM for crashing.
If good then install JB rom and test. Let us know.

unable to enter phone setting ？ then just simply look for a secsetting.apk for ur version then replace it n set the permission rw-r--r--

You could use adb to modify your build.prop
Sent from my SGNote

Makrilli said:
You could use adb to modify your build.prop
Sent from my SGNote
Click to expand...
Click to collapse
Bwahahah, now I see why you guys enjoy calling newcomers "noobs".
It was a computer problem. I just reinstalled JB 4.1.2 from my netbook and it worked.
Weird as hell though, given that I updated my GT-N7000 to JB 4.1.2 through Odin in this computer and it never gave me any problems.
I AM going to learn some ADB / Android SDK though. I'd rather learn everything before something like this happens to me again.
I appreciate everyone's concern, and thank you all for it.

nice to hear that you had this one fixed

Glad to hear its working now.

n7000 touchwiz home stopped
Zardonic said:
Bwahahah, now I see why you guys enjoy calling newcomers "noobs".
It was a computer problem. I just reinstalled JB 4.1.2 from my netbook and it worked.
Weird as hell though, given that I updated my GT-N7000 to JB 4.1.2 through Odin in this computer and it never gave me any problems.
I AM going to learn some ADB / Android SDK though. I'd rather learn everything before something like this happens to me again.
I appreciate everyone's concern, and thank you all for it.
Click to expand...
Click to collapse
hi.... im having the same problem as yours. i dont know what to do

lulu2050 said:
i had the same exact problem just few hours ago.....first of all you should boot into recovery mood by pressing vol up+ home button+lock button until samsung logo shows and then wipe all data/factory reset and wipe all cache partitions..........if that didnt fix it you should try rerooting it againg after re wiping
Click to expand...
Click to collapse
I have tried to upgrade my touchwiz to the new one, but got the danger message, would clearing the cache help?
Sent from my SM-N910C using Tapatalk

Please i need help, after flashing xposed framework, i cant booting my S5.

Hey everybody,
i hope so much, that anyone can help me. After i installed the recovery TeamWin (TWRP) (it was successful), i tried to flash Xposed Framework manually, i got again an massage "it was successful". But after that i can not start my Samsung Galaxy S5. It shows me only the Samsung Logo and nothing happened. Of course i tried via TeamWin an factory reset but i still can not boot my smartphone (Stop at the Samsung Logo). My S5 ist rooted, i`m using 5.0 (lollipop). Version of the TeamWin was 2.8.7.0 and of the Xposed Framework "xposed-v74-sdk21-arm". Has anybody an idea? I would be very happy. Should i delete the TeamWin recovery? But how? I want to install the standard recovery of Samsung, but how to do this? Where can i find the original Recovery from Samsung?

Xposed isn't supported on latest Android versions (r23). You should just remove Xposed from your phone, by using this tutorial:
Code:
http://forum.xda-developers.com/xposed/xposed-lollipop-stuck-bootloop-t3055816

Deadclysm said:
Xposed isn't supported on latest Android versions (r23). You should just remove Xposed from your phone, by using this tutorial:
Code:
http://forum.xda-developers.com/xposed/xposed-lollipop-stuck-bootloop-t3055816
Click to expand...
Click to collapse
Thank you, but i cant find the xposed folder...because i made a factory reset

Just delete the files and folders that you can see (those which are Xposed related). It should fix your problem.
Or just flash ovet your rom again (dirty, without wiping).
Sorry it took long time for me to answer.
Edit:
Read sticky, there's a script that uninstalls it automatically. This should work 100%

always make nandroid backup before flashing

Having the same problems
So I'm having the same problem. The Framework says it installs correctly, but after reboot, device gets stuck at the Samsung screen. I don't understand the comment android r23. I'm looking at the build info and I don't see this anywhere. Some explanation or assistance would be great.

I'm not sure why sdk 23 was even mentioned as Lolliopo 5.0 is sdk 21.
@LieberKerl, you got the xposed-v74-sdk21-arm.zip from Rovo89's thread, correct? If so this will not work on stock Samsung Touchwiz ROMs as mentioned in the first post of that thread.
There is no Xposed that will work on a stock Samsung Touchwiz ROM, it must be deodexed first and if you have a deodexed ROM, you need arter97's unofficial Xposed from this thread: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463.
If you don't know what deodexed is, there's a bit of reading ahead of you. If you don't want to deodex your Lollipop 5.0 ROM, then you're out of luck.

It takes longer to boot after the install, how long did you leave the samsung boot logo up? it took nearly 15 mins to boot after rom install and around 5 mins after xposed framework. I went through alot of hassle just to discover i was impatient.

Reflash stock ROM with Odin.

after flashing in my unite 3 notification bar disappeared and phone is restarting again and again

Nerotech11 said:
It takes longer to boot after the install, how long did you leave the samsung boot logo up? it took nearly 15 mins to boot after rom install and around 5 mins after xposed framework. I went through alot of hassle just to discover i was impatient.
Click to expand...
Click to collapse
Happened to me too on an Oukitel C4. After flasing it needs quite some time to boot.

Cannot Install Xposed in Samsung Galaxy S6
I have the same issue with a Samsung Galaxy S6. I tried installing "xposed-v87-sdk23-arm64.zip" using TWRP. But Every time I do it the phone either goes completely black or shows the Samsung Logo flickering permanently. To fix this I need to go into TWRP again and install "xposed-uninstaller-20160829-arm64.zip". I tried leaving the phone with the black screen/logo flickering for over 1 hour hoping it might be installing something but the only way to turn the phone back on is with the uninstaller.
I thought that it might be due to not having OEM unlock enabled, but I cannot find the option in "developer tools". Then I tried to do it through ADB command lines but when I enter the command "fastboot-windows oem unlock " it gets stuck with the message "waiting for device". So I also tried installing PdaNet both on my windows 7 PC and the phone itself (Android 6.0.1) and I made sure I have the phone drivers installed on my PC.
All I want is to use Xposed modules on my Galaxy S6. Is it even possible? If so, what should I do?
I appreciate any suggestions.
Thank you.

InfiniteSegovia said:
I have the same issue with a Samsung Galaxy S6. I tried installing "xposed-v87-sdk23-arm64.zip" using TWRP. But Every time I do it the phone either goes completely black or shows the Samsung Logo flickering permanently. To fix this I need to go into TWRP again and install "xposed-uninstaller-20160829-arm64.zip". I tried leaving the phone with the black screen/logo flickering for over 1 hour hoping it might be installing something but the only way to turn the phone back on is with the uninstaller.
I thought that it might be due to not having OEM unlock enabled, but I cannot find the option in "developer tools". Then I tried to do it through ADB command lines but when I enter the command "fastboot-windows oem unlock " it gets stuck with the message "waiting for device". So I also tried installing PdaNet both on my windows 7 PC and the phone itself (Android 6.0.1) and I made sure I have the phone drivers installed on my PC.
All I want is to use Xposed modules on my Galaxy S6. Is it even possible? If so, what should I do?
I appreciate any suggestions.
Thank you.
Click to expand...
Click to collapse
Most likely your issue is caused because you did not install the correct framework version. You need the one from wanam. Just search for "Xposed Samsung wanam" and you'll find your answer.

Umidigi BISON Boot Loop

Hi !
Mi cellphone worked well for one month and yesterday began restarting by itself, I tought It was a problem with the button ON; but today it gets worst, the phone doesn't restart to the menu home, it just keeps turning on in "Bison" and then it turns off, and again "bison" and turns off, here a link
I can't use the recovery mode because the times i reached it the phone turns off; there's a mode to block phone's turning off? maybe using some buttons?
Please I beg you, help.

i have got the same problem with my bison also ,on one month it was work properly bt nw restart it self every 4 seconds

can you give more information? Did you unlock the bootloader? Did you install another OS? Did you use Magisk?
Or was it a stock image with locked bootloader? And failed on its own? Its possible there was an OTA update but I cant tell with the info you supplied.

Hi, I just update the software from the provider (i think is a OTA update, a normal update).... and then the problem appears, it takes a few of days to show the bootloop; i dont do anything else.
Now im triying to flashing the rom but it's SO ****ing difficult, because the phone restarts always, but not completely.
I tried to use the default recovery mode, but the phone restarts...
I was thinking about some file to block the bootloop while flashing? it that possible?
Using the flash i just do download, and to finish the process it left just 3 files: supersu, cache and userdata, but it restaaaaarts :C ... i tried the option "upgrade firmware" but formating stops at 88% XD
I was thinking about a full format, it could be worse, no?

BuckyMalone said:
can you give more information? Did you unlock the bootloader? Did you install another OS? Did you use Magisk?
Or was it a stock image with locked bootloader? And failed on its own? Its possible there was an OTA update but I cant tell with the info you supplied.
Click to expand...
Click to collapse
YES, after that loop of boot problem,it came in normal after flash by SP flash(firmware upgrage),, then problem arose again,flash secondly by SP flash(formart all and download),this time it start normal but with another problem(TEE and google unwriten key,lost of IMEIs),i decide unlock bootloader and root it by magisk (follows umidigi comunity tutorial)bt all fail,it remain loop of booting it take more than 1mins show bison last log before start and shotdown again,,,off botton respond very slow on power on.

My Bison had this same infinite boot loop problem and I found out that the problem is in the short-circuited power switch. You have to open it and disconnect the flat from the side buttons to test

S10 Stuck on bootloop in AOSPK

Sooooooo..... I have a problem. I am using AOSPK, and everything went very well, I was very happy with my new custom ROM. The Equalizer App kept crashing, so I installed Viper4android. That didn't really work, so I tried to fix it by installing APKs, Magisk Modules, which all resulted in the driver not being enabled. But then I stumbled across this thread here on XDA and there was a Module for Magisk I could flash which supposedly fixed the Error, but of course, that didn't work. As usual, I removed it with Magisk and rebooted it.
Now. The thing is, I am pretty much stuck on an endless Bootloop. I already had a Bootloop once, but those always led me back to TWRP. To get out of the AOSPK Kraken loading GIF, I had to let it like that overnight and let it drain its battery. Now, this morning I plugged the Phone in and tried again, but it didn't work. I let the battery drain itself again, but It only took like 10 minutes as it was plugged in for a short time. I only now found out I can press on Power + VolDown to force reboot.
I would REALLY love some help here, how do I get out of this mess? Do I plug into a PC and try to boot to TWRP? What do I do next? Please explain to me step by step, I am really in a sticky situation right now.
UPDATE: I can get into TWRP, not what? I wiped chache and dalvik, did nothing. What now?

Hi. I am also using Kraken rom. Check out this post if you want.
[GUIDE] Go back to stock - Galaxy S10 series
Hi 🙂 So you have bricked your Samsung S10 series handset and you need it fixed. Sometimes we try to modify our phones and it goes wrong, fret not it can be restored. DOWNLOADS Frija Microsoft Visual C++ 2008 Microsoft Visual C++ 2010 Phone...
forum.xda-developers.com

puul said:
Sooooooo..... I have a problem. I am using AOSPK, and everything went very well, I was very happy with my new custom ROM. The Equalizer App kept crashing, so I installed Viper4android. That didn't really work, so I tried to fix it by installing APKs, Magisk Modules, which all resulted in the driver not being enabled. But then I stumbled across this thread here on XDA and there was a Module for Magisk I could flash which supposedly fixed the Error, but of course, that didn't work. As usual, I removed it with Magisk and rebooted it.
Now. The thing is, I am pretty much stuck on an endless Bootloop. I already had a Bootloop once, but those always led me back to TWRP. To get out of the AOSPK Kraken loading GIF, I had to let it like that overnight and let it drain its battery. Now, this morning I plugged the Phone in and tried again, but it didn't work. I let the battery drain itself again, but It only took like 10 minutes as it was plugged in for a short time. I only now found out I can press on Power + VolDown to force reboot.
I would REALLY love some help here, how do I get out of this mess? Do I plug into a PC and try to boot to TWRP? What do I do next? Please explain to me step by step, I am really in a sticky situation right now.
UPDATE: I can get into TWRP, not what? I wiped chache and dalvik, did nothing. What now?
Click to expand...
Click to collapse
Hi, don't know if it's too late but I did have the same problem before and all I did was boot into TWRP. When you wipe make sure to check everything from Dalvil to Internal Storage and format data as well. Also if you are going to install Magisk try to do it after your phone boot into os otherwise it will stuck in bootloop again. I hope that's can help!