Database Info

[Q] Bricked SGS4G

Hi, i got this Samsung G S 4g. I was supposed to fix the rom (somewhat unstable thing). I will try to write all the things i have done until now. I got the "phone to pc" icon. I cannot boot or use download mode (the triangule thing)
General Info
Device is rooted. T-mobile branded, carrier-locked.
Froyo rom. (i think is stock but rooted).
Somewhat old device.
Had stock recovery (Android recovery e3 o something like that)
SGH-T959V (KB5)
Things i did
1. Pull some files from device, to sim-unlock. (using ADB) DID not modify anything else
2. SIM-Unlock using code (worked)
Then, device worked ok some weeks... then stopped working, contacts and phone apps crashed suddenly, everytime i open them
4. Use lastest Heimdall and this guide to get CWM on the phone. The idea was to flash the kernel. did not work. Check the part called "How To Flash a Kernel with Heimdall".
I did that. NOTE: used this kernel insted of the "old" one that the guide says.
Then it output this error: "libusb error: -12". So Heimdall didn't detect the device so i used zadig.exe after reinstalling the samsung drivers to avoid this issue. Then, it started working, and output something like this: "failed sending file part packet heimdall"
And now i have this:
{
"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"
}

What you have is an alternate form of DL mode that occurs after a failed flash. Read this to get back up and running.
Lumins Guide

Or just reboot the phone, it should go to a disturbing looking tiny-phone mode. Then just resend your heimdall command and it should happily work.

Major kudos to diego930 for such a nicely detailed description of his problem!

Yes... my computer didn't feel like showing the tiny disturbing phone this morning, else I could have skipped the suggestion to reboot.
That just means that the safeties are off and your phone is ready and waiting to get flashed. You're close... and probably got fixed, based on the thanks provided.

Theraze said:
Or just reboot the phone, it should go to a disturbing looking tiny-phone mode. Then just resend your heimdall command and it should happily work.
Click to expand...
Click to collapse
How i do reboot ? I just get the phone to pc icon everytime lol
jeffsf said:
Major kudos to diego930 for such a nicely detailed description of his problem!
Click to expand...
Click to collapse
Thanks I like making myself very clear (and i know how annoying is the lack of info)
I haven't touch the device since i broke it so i'm going to try that guide and post any news. Thanks all!

When you get that phone to pc icon, just use Heimdall to flash again.
The reboot-step is from official-download mode where it has the big yellow caution taking you to panic-download mode where it has the tiny phone you posted in #1. Once you have panic-download mode, your phone is ready to accept anything. Even whatever failed before.
Summary: Repeat OP Step 4.

ok, done. Fix using heimdall 1 click! I just reflash GB with kernels and bootloaders, now it works flawless.
Thanks Theraze.

[Q] Urgent Help

Hi Guys,
Have literally spent 8 hours trying to fix this damn phone, it's my mothers which needs a complete wipe using the stock rom. Even my younger brother had a go for a week and has been passed on to me. Not touched an Android phone in about two years so very rusty with the whole roms and flashing etc.
The main issue is I can't get Windows 8.1 to see the phone in USB wether it be plugged directly in Android, USB debug, bootloader or Fastboot USB. I have installed ADB with all the drivers, tried multiple HTC drivers and HTC Sync, PDAnet, AMD chipset drivers, USB controller drivers, random drivers from here on XDA as well as a multitude of other sites. Tried USB 3.0 and 2.0 (front and back slots).
How am I supposed to flash a custom recovery without the computer seeing the phone? If I can just get that sorted I am pretty much set with getting the stock rom on there and the rest. Not sure what my brother has put on it or if he has flashed a custom rom or changed the radio/boot because I have no clue what the phone is supposed to be running.
Please some help here, don't really want to be spending more time on this.
Details:
{
"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"
}

I'm not sure how to help you, because i don't even know, if your phone boots to OS or not.
There are some apps out like flashify or TWRP Manager which should be able to flash a recovery from OS, but i never used that tools and don't know, if they work with One SV.
You should really get your fastboot working. I don't have windows 8(.1), but there are many threads here on xda about that.
Other solution could be to search for someone with a windows 7 pc.

old.splatterhand said:
I'm not sure how to help you, because i don't even know, if your phone boots to OS or not.
There are some apps out like flashify or TWRP Manager which should be able to flash a recovery from OS, but i never used that tools and don't know, if they work with One SV.
You should really get your fastboot working. I don't have windows 8(.1), but there are many threads here on xda about that.
Other solution could be to search for someone with a windows 7 pc.
Click to expand...
Click to collapse
Yes the phone does boot into the OS but again is not properly recognized, PDAnet and HTC Sync find the phone but doesn't show up or in ADB. I have checked well over 30 threads on here regarding Windows 8.1, downloading various tools and drivers etc without success.
Will check out those links.
Thanks.

[Q] Encryption Unsuccessful & Bootloop - GT-P3100 Tab2 7"

Hey guys! i have an issue here. can anyone help me solve this problem.
before i started getting this error i had, they were working well
- AOKP 4.4.4 custom rom
- Philz touch 6.0 Recovery.
from few days i started getting this error, see image
{
"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"
}
I tried to flash stock firmware, i downloaded two firmware of INU region (India)
everytime i get the following error on odin,
(Above pic for reference only. im using odin v3.09 and latest)
I tried flashing with PIT files, it didnt work.
I tried flashing TWRP, CWM it flashes recovery but when i go to recovery then still philz is there.
I searched on many forums and Googled, and i came to know that my /data and /sdcard is corrupted. but i can access the content /sdcard from recovery and i can view my files.
I tried flashing other custom rom. It flashes them without any error but when i reboot my Tab its not flashed. its same.
What to do please help me.

Ok so after doing so mush research on this on xda, gsm-hosting, google, etc....
i came to a conclusion that the emmc is corrupted or right protected (Means It has become read only). which is why we are unable to flash through odin or through recovery. even if the flash is successful then after reboot the TAB returns to the earlier state i.e same rom, bootloop and recovery.
so there are three way you can fix it:
1. change motherboard, which is very costly. on ebay it was 13k (India). dont know about local shops or service center. but im sure it will be more or less same.
2. Change emmc. ask the repair guy to change the buggy emmc to a new one. buy the emmc from alibaba online store or other online stores if you cant find it offline.
3. You can get back the same tab to work by directly flashing the stock rom directly to emmc. This process involves soldering the pins of the tab and flashing directly on to the chip using a box called ATF (Advance turbo flasher). This process is little advance, one can do it if you know what pins to solder (You can get the idea from youtube & gsm hosting), but buying atf box would be costly. costlier than the emmc replacement. now if you want to experiment and learn you can go buy a atf and revive your dead tab (it will be called The walking dead. ).
:)
so i am replying to my own thread so that if any body is comes searching for the same gets to know what happened and what to do next.
BTW Android_Andi has done some great research on this he tried every possible thing but unfortunately it didnt work. Thanks to him for his time and effort.
and if anybody figures out how to fix it without using atf box please do post and let me know. because im keeping my dead tab with me and if someone knows any alternate way i can fix mine too. who knows anything can happen.

Bootloop on Samsung Galaxy S3 with TWRP and Lineage OS 17.1

Hello guys, so basically you are my last hope since I cannot find a solution for my problem (at least with my level of knowledge).
Lets start from the beginning: I (someone with no experience in this topic) decided to try out a new OS on my old Samsung Galaxy S3 since a lot of apps stopped working on Android 4.3. I tried a tutorial on youtube on how to install a new custom ROM. I installed TWRP (3.5.2_9-0-i9300) and later with the help of TWRP Lineage OS 17.1 (an unoffical version for my type of phone) and everything worked perfect.
I started to download all apps I need and to customise my OS. In the end when everything was set up I decided to do a full backup using TWRP and thats where the problem started. In the development section I checked the function, that when you press the power button you can directly boot your phone into recovery mode. So my phone rebooted and ended up in a constant boot loop where at first the Samsung Galaxy logo appears (first picture) and then TWRP appears (second picture) and this process goes on and on...
{
"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"
}
Sadly there is no way to get into recovery mode since this loop just continues. If tried it many times also with taking out the battery and putting it back in. The only thing I have access to is the download mode.
So my question to you: is there anything I could do in the download mode to solve this problem? I saved the important data before so a full wipe wouldnt be a problem. Maybe I can do something with odin?
I really hope you can give me some ideas to try out. Every help is appreciated. Thanks!

Try reflashing a stock ROM first of all.
Then reflash TWRP. Make a TWRP backup (especially the EFS ! That is a "must-do first and foremost" !) of your working system and progress from there.
And in the future, instead of reinstalling all your apps piecemeal I strongly recommend you use Titanium backup (paid version. The free version is very limited), that is a wise invesment for the small sum it'll cost you

@Snakeforhire reflashing stock ROM worked, thank you so much.
I will take a closer look on Titanium backup. Used it in the past but with root access. On the new Lineage OS I dont have root although it shouldnt be hard to get from what I read.

Lenovo Legion Duel Not Working Anymore

So recently my phone was having minor problems.. like randomly restarting and showing overheating warning when the phone isn't even hot.. so ive decided to update it through RSA but turns out RSA dont have the update my phone needed.. I've tried multiple update but not even the china one works even though the phone was originally from china.. can anyone please help.. I'm so sad right now because i dont want to loose this phone
P.s after installing the update from RSA the phone just stuck in boot up then cuts of after
{
"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"
}

You have a Pro not a Duel. You will need this first, extract it and place all the files within it to /ProgramData/RSA/Download/romfiles/L79031(delete whats currently in this folder first, then move all the files you downloaded into this folder). Now run RSA and and flash the correct firmware for your Legion Pro. Upon boot, make sure to run System Update to the latest firmware available (you will have to do this two or three times).

&(*) said:
You have a Pro not a Duel. You will need this first, extract it and place all the files within it to /ProgramData/RSA/Download/romfiles/L79031(delete whats currently in this folder first, then move all the files you downloaded into this folder). Now run RSA and and flash the correct firmware for your Legion Pro. Upon boot, make sure to run System Update to the latest firmware available (you will have to do this two or three times).
Click to expand...
Click to collapse
I think I'm in the same situation- And your link doesn't work. What is 'this'? Can't find any info on it!!!

@xXHotBoxXx420 ,
Pretty sure that link was removed. Here is where you'll find the firmware for your device. Just follow the instructions you quoted by @&(*) after gathering your models firmware.

project_2501 said:
@xXHotBoxXx420 ,
Pretty sure that link was removed. Here is where you'll find the firmware for your device. Just follow the instructions you quoted by @&(*) after gathering your models firmware.
Click to expand...
Click to collapse
Hey thank you, but I actually found a CN ZUI 13.5 ROM that I've never found before and flashed it, and it worked. I have Android 12 now, but my cellular still isn't working, and I want a ROM with Google apps by default- one more like the stock android. I assume that's the global version. Trying to go about unlocking my bootloader and flashing the Legion Duels ROM on my Legion pro, I've heard there is a way. Just need to find a good tutorial.

@xXHotBoxXx420 ,
Here is a guide that will work on this device, make sure you read it carefully and backup what it states. I suggest you read this other guide first so you can recover from any mistakes.

project_2501 said:
@xXHotBoxXx420 ,
Here is a guide that will work on this device, make sure you read it carefully and backup what it states. I suggest you read this other guide first so you can recover from any mistakes.
Click to expand...
Click to collapse
Helpful, but I'm wondering if I can do it the other way around; CN to Global rather than Global to CN. I'm sure it probably works the same way, backup partitions and all that. I just figured you had to unlock the bootloader to be able to flash other ROMs but I have flashed the ROW & EE ROMs and ended up with crashdump/bootloop. Didn't realize flashing partitions could fix that. I think I'll give it a try. Thanks