Develop Bugs

[Q] GT-N7100 Soft-Brick

Hey Guys
1- I'v rooted my GT-N7100 long time ago (couldn't remember the method but the developer said the methood doesn't make any alteration to your device, Just root privilege. even doesn't install CWM)
2- I'v installed CWM through "ROM Manager" android app last week.
3- Installed some 4.4.2 ROMs but all unstable, crashing in few minutes. (All the ROMs got good comment 'n I think there is a problem with my device!!)
- DN3 (Ditto Note 3) ROM
- JellyKatv4
- CM11 ROM for Galaxy Note 2
- BLUE LIGHTNING
4- Decided to flash official 4.3 firmware downloaded from: "http://www.sammobile.com/firmwares/3/?download=12202" through ODIN, but got "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“ message.
5- Decided to unbrick with ODIN, but every-time it fails (tried different ODIN versions 'n different USB ports)
6- Tried to do so with KIES, but it does not recognize the device (Stucks on connecting message, troubleshooting doesn't effect). Also tried "Tools> Firmware Upgrade and Initialization" option directly, It crashes in EVERY STEPS.
So if u have any Idea to fix this, please share!
Afshin

lazzara said:
Hey Guys
1- I'v rooted my GT-N7100 long time ago (couldn't remember the method but the developer said the methood doesn't make any alteration to your device, Just root privilege. even doesn't install CWM)
2- I'v installed CWM through "ROM Manager" android app last week.
3- Installed some 4.4.2 ROMs but all unstable, crashing in few minutes. (All the ROMs got good comment 'n I think there is a problem with my device!!)
- DN3 (Ditto Note 3) ROM
- JellyKatv4
- CM11 ROM for Galaxy Note 2
- BLUE LIGHTNING
4- Decided to flash official 4.3 firmware downloaded from: "http://www.sammobile.com/firmwares/3/?download=12202" through ODIN, but got "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“ message.
5- Decided to unbrick with ODIN, but every-time it fails (tried different ODIN versions 'n different USB ports)
6- Tried to do so with KIES, but it does not recognize the device (Stucks on connecting message, troubleshooting doesn't effect). Also tried "Tools> Firmware Upgrade and Initialization" option directly, It crashes in EVERY STEPS.
So if u have any Idea to fix this, please share!
Afshin
Click to expand...
Click to collapse
Verify you've correct drivers installed and a working USB cable. Have you tried flashing your phone under PDA Tab? With only 'Auto Reboot' checked.
Odin v3.07: https://www.google.com/url?q=http:/...ds-cse&usg=AFQjCNEs2NnDVm8eh5Fkl5x_eCDMptJLAg
Drivers: http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows

The sime thing to me
I instal philz recovery from odin
Thin instal wanam room fron recovery
After update to 4.4.2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
أرسلت من SM-N9005 الخاص بي باستخدام تاباتوك

did you manage to recover your device? I have same problem and nothing helps to recover my handset What the screen displays on your device in DL mode? can you put your device into bootloader mode?

finally recoverd my phone
Went to an expert 'n he gave me a 4 file 4.3 firmware package 'n it works for me, but I feel the official 4.3 firmware is too slow on my device!?

[SM-T310]Frequently Asked Questions

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This a short list of frequently asked questions about the Samsung Galaxy Tab 3 8" (SM-T310) and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses.
Do not use this thread as a general helping thread.
Q1: How do I root my SM-T310?
First you're gonna need a custom recovery installed.
Download the following files to your computer: Odin, TWRP, Root
Extract Odin into a new folder and then TWRP in Odon's folder. After that's done start the Odin tool and put your device into download mode. To do this, power it off and hold the Home + Volume Down + Power buttons until you see the warning screen.
Once that's done, connect your device to your computer and wait till Odin recognizes it. If it doesn't usually an installation of Samsung Kies would fix it.
After the device is recognized sucessfully click on the PDA button in Odin and navigate to the TWRP file location and load it.
Wait for the PASS message and reboot your device. (Without disconnecting it)
Once done, boot into TWRP and hold your device in portrait mode, tap Reboot on the bottom right of the screen and then select System on the next menu.
Once you do this you will be asked to install root. If that doesn't work for your, copy the Root zip file to your SD Card, boot into TWRP and flash it as a normal zip.
Click to expand...
Click to collapse
Q2: How can I enter recovery?
To enter recovery, power off your device and hold Power + Volume Up buttons untill you see the Samsung Galaxy Tab 3 splash screen and let off the Power button untill it boots you into recovery.
Click to expand...
Click to collapse
Q3: Which is the best ROM/Kernel?
Honestly, there is no "best". It's all based on personal choice. For example; I may like heavily customizing my ROMs whereas you may like it to look at basic as possible. The best thing you can do is to just test out different ROMs/kernels/modems and see which you prefer.
Also, please don't ask which is the best because your post will be deleted as it's against forum rules.
Click to expand...
Click to collapse
Q4: Am I required to backup my data before flashing anything?
No you're not, but it is definitely a good idea, especially when flashing a ROM with an updated base, because if you don't do a backup and then something goes wrong, it means that you'll lose all your apps, data etc.
Click to expand...
Click to collapse
Q5: Does this device have a good battery life?
We all have different apps installed, use our phones for different amounts of time, have different ROMs and kernels installed etc. so we will all experience different results regarding battery life.
Click to expand...
Click to collapse
Q6: I'm not sure whether to get the Samsung Galaxy Tab 3 8"/what other tablets compare to the Tab 3 8"?
The only person who can make you want the device is you. If you're not sure whether to get this tablet, go to your local devices shop which has stock and have a test run of it for yourself. If you're not sure what device to get and want to compare between your choices, please use the following thread - Device Suggestion Thread
Click to expand...
Click to collapse
If you have any suggestions regarding this thread's content, feel free to post them.​

+1 For this Mate. :thumbup:

[Need Help] ZE551ML Bootloop and No Fastboot

So, recently I tried to use this ROM: http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526
after revert back from CM13 custom ROM: http://forum.xda-developers.com/zen.../rom-cyanogenmod-13-0-nightly-builds-t3264492
But the result is my phone stuck in Asus logo.
Tried to access recovery by pressing power button + volume up but cannot go into recovery.
Tried to connect phone to PC via USB cable but the phone is not detected (cannot try fastboot from PC).
Here is what I did before my phone bricked:
1. Reboot into recovery (I'm using TWRP)
2. Wipe everything except MicroSD
3. Install SuperSU (downloaded from the thread)
4. Install ROM v168 (downloaded from the thread)
5. Reboot system
After that my phone stuck in Asus logo.
Tried to search solution from many sources still no luck. Already posted in the thread but still no answer from anyone.
Please help because I don't have backup phone :crying:
Thanks.

Did you really flash supersu before you flashed the Rom? That's probably the cause. Have you tried any of the bootloop solutions posted here yet?
Sent from my ASUS_Z00A using Tapatalk

If you cant go recovery try using this method..
It goddamn works ��
Requires sometime to understand it though. But you'll get it ��
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256

Vinaygan said:
If you cant go recovery try using this method..
It goddamn works ��
Requires sometime to understand it though. But you'll get it ��
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Click to expand...
Click to collapse
Yup, tried this method and my phone is resurrected.
But the content of that tutorial was hard to understand at the beginning

kenbo111 said:
Did you really flash supersu before you flashed the Rom? That's probably the cause. Have you tried any of the bootloop solutions posted here yet?
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I've followed the steps provided in the thread so I assumed that superSU was flashed already.
How to verify if it's flashed or not? Can I verify before moving on to the next step?
My phone is resurrected now thanks to steps provided by summit.
Could it be because I was using TWRP before?

i had problem like you. i dont have bootloader and fastboot. i use xFSTK-Downloader.
success.
i can help you
fb: facebook.com/hieulanhat123
sorry my English i am from vietnam

I tried the summit method on a Win10 machine but it doesn't detect the phone on xFSTK-Downloader, can somebody help me?
This is how the phone looks right now:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

arturocr said:
I tried the summit method on a Win10 machine but it doesn't detect the phone on xFSTK-Downloader, can somebody help me?
This is how the phone looks right now:
Click to expand...
Click to collapse
Bruh...
I've successfully recovered my phone using xFSTK
On a win10 os
---------- Post added at 02:01 PM ---------- Previous post was at 01:50 PM ----------
arturocr said:
I tried the summit method on a Win10 machine but it doesn't detect the phone on xFSTK-Downloader, can somebody help me?
This is how the phone looks right now:
Click to expand...
Click to collapse
1. Make sure your device shows up for awhile during boot
(when the phone vibrates upon boot)
2. Make sure you selected MOOREFIELDS.
3. Once done selecting the files " change the gp override flag under OPTION to 0x80000807"

Need help with hardbricked phone

Hi, something went wrong while trying to install pixelExperience on my redmi note 8 pro. It doesn't reach any screen, no fastboot, no recovery, no boot screen. The notification led light up when connected to the PC, but no charging screen.
I was installing pixelExperience 11 with no error, but it never booted up after rebooting.
I'm currently trying to flash rom downloaded from xiaomifirmwareupdater.com with SP flash tool. I'm using the version from UnbrickRN8ProNoAuth, it says it worked, but the phone won't start.
The booloader was unlocked, I tried both the global and the europe version. I don't know what to try now, any suggestion ?
What could be the problem, I was expecting that flashing the official rom would at least get me to the boot screen.
Thanks !

Hello to me, exactly the same thing happened to me when installing pixel experience, you follow all the steps of UnbrickRN8ProNoAuth
to use python, driver, libusb, bypass and finally spflashtool with the dafiles and the authfiles?
I use the version with this method is this:
https://c.mi.com/thread-3612344-1-0.html
With that I was able to start the mobile and the fastboot mode worked again, apparently it is a bug when entering pixel experience if you have firmware 12.5 that sometimes causes the brick, try that version it worked for me. a greeting
ps: especially remember to use the auth_sv5.auth in the program
and MTK_AllInOne_DA_mt6765_mt6785, if everything is correct you should get a green check, I tell you because first the program checks the rom if it is correct, do you connect it by pressing the 3 buttons at the same time?

Hey, thx, I'll try with this version then !
Yes I have the green check, and I connect the phone with only the vol+ pressed.
I need to do the bypass every time, is that the normal behaviour, and is there another step I should redo ?

robicop2 said:
Hey, thx, I'll try with this version then !
Yes I have the green check, and I connect the phone with only the vol+ pressed.
I need to do the bypass every time, is that the normal behaviour, and is there another step I should redo ?
Click to expand...
Click to collapse
Because of the preloader mode I never use volume + I always use the 3 buttons, so I added the "libusb filter" the bypass I don't know exactly what it is for, but the 2 times that I used the mediatek program and I used it, I just look at it, and according to github it is used for: "Small utility to disable bootrom protection (sla and daa)" and according to google the bootrom: "Bootrom (or Boot ROM) is a small piece of ROM mask or write-protected flash embedded inside of the processor chip. It contains the first code that the processor executes when turning on or resetting. "Enteoria, if it doesn't write you that data from version 12.0.4, it doesn't turn on, follow all the steps correctly with the rom that is shared with you. above and I should start your phone.

It's working again !!
I searched for a similar version but global, and installed it (https://c.mi.com/thread-3565279-1-0.html)
Thanks a lot.
If that can help someone, this time I had an error on the 4th step, it wasn't finding my phone whereas the step 5 could. I had to rerun step 3.
Now I have to choose between settling with this version or trying again ^^ did you manage to install pixelExperience in the end ?

Hi, I'm glad you fix it in the end, the rom that you put is the same, it only changes that mine is the europe version and yours is International, the google patch also changes,
In the end, if I could install pixel from 12.0.4 to pixel 12, from 12.5 the firmware is different and there are many bricks, I bricked myself just like you did not turn on anything, when going from 12.5 to pixel 11, from 12.0 no It opens up risks of going to pixel 11 or 12.
in the end, you can only install pixel 12, wanting to put 11 could not mount the system and the provider
The problem that the cameras do not work well in pixel, even installing gcam they go lag and not all of them work, not even the 64mpx mode, right now I am in miui stock with bootloader closed again. the cameras are important to me, greetings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Can't install recovery

I've got an s4 i9195l (is this jfvelte or serronoltexx ?) and I had twrp 3.x.6 installed and an android 10. I used a backup I had of my original stock phone and flashed it back. It went back to the samsung rom and recovery.
Whenever I try to install any recovery above twrp 3.0.2 it installs OK but when I try to boot into it I get the download robot and a message about it not being able to boot properly.
If I boot into the rom (android) I get back to the samsung recovery, or if I go straight to download I can easily reinstall 3.0.2.
I can't seem to get any roms to install from twrp 3.0.2 either.
Does anyone have any ideas how I can sort this? I found android 10 sluggish so I wanted to drop back a couple of releases.
Thanks
EDIT: I should add I have been using linux and heimdall. I did try in odin with windows 8 and 11 too. I've also tried updating twrp from within twrp and still no joy.

Your phone should be a serranovelte. This shoud be the suitable TWRP-versions:
Downloads for : Samsung Galaxy S4 Mini | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com

DevaVictrix said:
I've got an s4 i9195l (is this jfvelte or serronoltexx ?) ...
Click to expand...
Click to collapse
Model GT-I9195I is not an S4. It is an S4 Mini. Furthermore, it's distinguished from the earlier original S4 Mini by the upper case "i" at the end. It's sometimes call'd S4 Mini Plus, or S4 Mini Value Edition. Neither jfvelte nor sorranoltexx is correct for the I9195I, which is instead known as serranovelte (where the "ve" is for Value Edition).
Have you tried the TWRP and latest LineageOS developed by mernurisha? Look here:
[ROM][11.0][12L][UNOFFICIAL][MicroG support]LineageOS 18.1/19.1 [SERRANOVELTE GT-I9195I]
Ephemeral shortcuts Hello everyone, Thanks for this version of Android 11. However, I have a little problem with the shortcuts. They disappear after a restart for applications moved in external memory on the SD card. On the other hand, the...
forum.xda-developers.com

MrGoodtunes said:
Model GT-I9195I is not an S4. It is an S4 Mini. Furthermore, it's distinguished from the earlier original S4 Mini by the upper case "i" at the end. It's sometimes call'd S4 Mini Plus, or S4 Mini Value Edition. Neither jfvelte nor sorranoltexx is correct for the I9195I, which is instead known as serranovelte (where the "ve" is for Value Edition).
Have you tried the TWRP and latest LineageOS developed by mernurisha? Look here:
[ROM][11.0][12L][UNOFFICIAL][MicroG support]LineageOS 18.1/19.1 [SERRANOVELTE GT-I9195I]
Ephemeral shortcuts Hello everyone, Thanks for this version of Android 11. However, I have a little problem with the shortcuts. They disappear after a restart for applications moved in external memory on the SD card. On the other hand, the...
forum.xda-developers.com
Click to expand...
Click to collapse
Nice to hear! I have the same problem on Samsung S4 GT-I9195I kitkat 4.4.4 and an ubuntu 20.04 with adb and heimdall installed. Do you think I am using the wrong recovery version?
Is this the version serranoveltexx ?
My procedure
Turn off Phone by long pressing the Power button;
Boot into Recovery mode (Home + Volume Up + + Power)
Wipe /data – Factory reset
Wipe /cache
Reboot and quickly after hitting reboot, into Download mode (Home + Volume Down + Power)
Code:
sudo heimdall detect
getting the img file from here.
Code:
sudo heimdall flash --RECOVERY twrp-3.7.0_9-0-serranoltexx.img --no-reboot
Volume down + Power to restart manually
Home + Volume Up + Power to boot into recovery mode
But what I get is the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

giammi56 said:
... Do you think I am using the wrong recovery version?
... flash --RECOVERY twrp-3.7.0_9-0-serranoltexx.img
Click to expand...
Click to collapse
Yes, clearly the wrong TWRP image because it lacks the "ve" which identifies your GT-I9195I model. As to whether your link is correct, I can not say because I'm still using TWRP v3.4 from ~2.5 years ago (works for my purposes). Your best bet would be to use whatever recovery is link'd in the first post of mernurisha's thread re LOS 18.1 & 19.1 (see link to mernurisha's thread in post #3 above).