I was using Odin trying to flash this stock rom to my device, then i felt like its doin nothing so i disconnected it.
Here are the instructions I've followed.
now i see this image, no recovery or download mode avail:
{
"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 found this post, but since it targets Galaxy S and not my device (Galaxy S WiFi 5.0 YP-G70 Player - US version), I am not sure about OPS File mentioned there, is it device-independent?
I don't wanna make things worse than they are now.
Update
I've managed to unbrick the phone, now I'm unable to flash a ROM on it, see details.
Thanks for your help.
Been there, done that.
http://forum.xda-developers.com/showthread.php?t=1386669
Go to this guide. Get the bootloaders he provides. You'll use his PIT file and bootloader to get back to the download screen. Then flash that stock rom you were trying to flash previous, but use the PIT file you used from AdamOutlers guide. Should come back perfectly fine.
DeLaVicci said:
http://forum.xda-developers.com/showthread.php?t=1386669
Go to this guide. Get the bootloaders he provides. You'll use his PIT file and bootloader to get back to the download screen. Then flash that stock rom you were trying to flash previous, but use the PIT file you used from AdamOutlers guide. Should come back perfectly fine.
Click to expand...
Click to collapse
It requires an Ubuntu box.
I would do it if I don't have another choice.
I thought about using the Odin Multi Downloader from PC.
Update: Will this work for my particular device so I don't have to install Ubuntu? He talks about a windows version (with a exe extension), but i dont find the download and its not on google code.
Update: Found the exe:
http://code.google.com/p/heimdall-o...mdalloneclick/resources/HeimdallPackage/?r=27
NullUser said:
It requires an Ubuntu box.
I would do it if I don't have another choice.
I thought about using the Odin Multi Downloader from PC.
Update: Will this work for my particular device so I don't have to install Ubuntu? He talks about a windows version (with a exe extension), but i dont find the download and its not on google code.
Update: Found the exe:
http://code.google.com/p/heimdall-o...mdalloneclick/resources/HeimdallPackage/?r=27
Click to expand...
Click to collapse
Notice that I didn't follow the guide, it just led me to trouble.
All I had to do is install Java, run the jar and let it do its thing, didnt have to bother with permissions or extracting the jar at all.
No, ignore the Ubuntu part. Just download his GalaxyPlayer-Bootloader.zip. Skip the instructions for the Resurrector, it's not needed. Just start the guide at step 4, and it should get you into download mode. Then flash the stock ROM you got, but flash without a PIT file. It's the PIT file that made it crash, I've had the same problem.
DeLaVicci said:
No, ignore the Ubuntu part. Just download his GalaxyPlayer-Bootloader.zip. Skip the instructions for the Resurrector, it's not needed. Just start the guide at step 4, and it should get you into download mode. Then flash the stock ROM you got, but flash without a PIT file. It's the PIT file that made it crash, I've had the same problem.
Click to expand...
Click to collapse
Whatever, it's already in download mode (i used that OneClick.jar, ran it and followed it and it unbricked it).
Anyway, now I'm trying to flash the ROM using Odin, I'm starting the process and it goes idle, here is the Odin log:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ueki8_min.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
************Here is where it standing right now and doesn't do anything************
i checked the cpu and its 0%, is the device working? how long can it take?? As soon as I disconnect, it will go soft-bricked, which is what happened last-time, is there any point in being patient and letting it work, i dont see any progress or sign of life anyway.
Update
I looked into Heimdall but have no clue how to flash a stock rom with it, all i got is a pit file and a md5 file.
UPDATE
Case closed, I found the problem, it was the PIT file, I took a PIT from here and everything works like a charm!
Thanks for all of you!
I kept telling you it was the pit file.
Can you help me?
I had the same thing as you. Used oneclick.jar and unbricked, but now when I try to flash Erygits rom Odin says FAIL and something with blablabla pit.
What do I do now?
BTW how did you flash with Heimdall (or didn't you?)?
Thanks in advance.
Rapydax said:
BTW how did you flash with Heimdall (or didn't you?)?
Click to expand...
Click to collapse
I flashed with OnClickUnbrick which is part of Heimdall.
Did you unbrick your device already (and bring it to download mode)?
No - refer to here.
Yes -
You'll have to know if you have the US, International or EU version. FYI, The US version has a capacitive (non-physical) home button.
Install Odin
Make sure the Samsung Driver is installed (check device mgr)
Use a PIT from here
For the US version: Use this (2.3.5) or this (2.3.6), or this ROM (all ROMs are rooted)
For international use one of the ROMs here.
I'm just trying to help, I'm not resp. for any damage etc. etc. etc.
If you have a different device, or u need any other help, buzz me and will provide links, I have some, in just a few ago I didn't have a clue what a ROM means, so don't be shy to ask, and sorry if that's not the case.
And BTW, should u ever hear about a tested ICS ROM for the US ver. please PM or buzz me.
DeLaVicci said:
http://forum.xda-developers.com/showthread.php?t=1386669
Go to this guide. Get the bootloaders he provides. You'll use his PIT file and bootloader to get back to the download screen. Then flash that stock rom you were trying to flash previous, but use the PIT file you used from AdamOutlers guide. Should come back perfectly fine.
Click to expand...
Click to collapse
If you have the Phone-PC screen, you don't need bootloaders. The Phone-PC screen is "forced" download mode - device is saying "you need to flash something in Odin"
Unable to have device boot after following all suggestions
First I want to thank all who have made possible either by developing or recollecting the data required to unbrick the Samsung Galaxy Player 5.0, an excellent effort!
Let me know explain my device situation:
1. I got the Galaxy Player 5.0 US (capacitive buttons) from a friend (original owner) who I think he did try some trick (he couldn't explain) and the device never booted again.
2. I've been researching the different tools, files, kernels, factory ROMs around the Galaxy Player 4.0 and 5.0.
3. I've patiently read gazillion threads in this forum which all of the interconnect at a given time, from there I was able to finally identify and download:
Tools required:
- UnBrickable Resurrector - Adam Outler
- VirtualBox VM with Windows 7
- GalaxyPlayer Bootloader package
- Odin
- Heimdall
I have downloaded the ROM:
- YP-G70_UEKI8_MIN.rar
- Eryigit_Rom_PDA_YP-G70_G70ZCKPA.R.3.0-Defult-USA-Extract-it.rar
which only includes the kernel (zImage) and the filesystem content (factoryfs.rfs) and the pit file (euki8.pit).
I've find the euki8.pit to be useless in the many attempts to try to flash using it (Odin will stall the process of flashing if I use it); instead of it, I've downloaded:
- G70-GalaxyPlayer5.0-8gig.pit
- GB70-GalaxyPlayer70-16gb.pit
I don't know if it is a 8 or 16 gig, since I never used the device.
What is the condition of the device?
- The device will not show a charging icon when charging cable is connected (either to the USB power adaptor or the computer USB port)
- The device will get warm if I connect the charger to the wall outlet
- The device screen does not react to pressing the Power button
- The device screen does not react to pressing Vol Up/Down and Power (Download Mode)
What I've accomplish so far:
- Device is able to go to Download Mode using the UnBrickable Resurrector.
- Use Oding to transfer files to the device while in Download Mode.
Data Transfers Successfully attempted:
- Download Mode only:
- Put device in Download Mode using UnBrickable Ressurector.
- PIT File included in Galaxy Player Bootloader package
- Selected to Re-Partition
- Used the Bootloaders included in the GalaxyPlayer Bootloader package.
Transfer reported by Odin as pass, the device behavior is exactly the same as originally described.
- Partition / Boot
- Put device in Download Mode using UnBrickable Ressurector.
- PIT files (G70-GalaxyPlayer5.0-8gig.pit and GB70-GalaxyPlayer70-16gb.pit)
- BootLoader from GalaxyPlayer Bootloader package.
Transfer reported by Odin as pass, the device behavior is exactly the same as originally described.
- Partition / ROM
- Put device in Download Mode using UnBrickable Ressurector.
- PIT files (G70-GalaxyPlayer5.0-8gig.pit and GB70-GalaxyPlayer70-16gb.pit)
- BootLoader files from GalaxyPlayer Bootloader package.
- ROM file ueki8_min.tar.md5
Transfer reported by Odin as pass, the device behavior is exactly the same as originally described.
- Partition / Boot / ROM
- Put device in Download Mode using UnBrickable Ressurector.
- PIT files (G70-GalaxyPlayer5.0-8gig.pit and GB70-GalaxyPlayer70-16gb.pit)
- BootLoader files from GalaxyPlayer Bootloader package.
- ROM file ueki8_min.tar.md5
Transfer reported by Odin as pass, the device behavior is exactly the same as originally described.
- ROM
- Put device in Download Mode using UnBrickable Ressurector.
- ROM file ueki8_min.tar.md5 and Eryigit_Rom_PDA_YP-G70_G70ZCKPA.R.3.0-Defult-USA.tar
Transfer reported by Odin as pass, the device behavior is exactly the same as originally described.
I've also tried using Heindall without success, most of the time the communication breaks and I see a lots of communication error reported back from libusb. So far the only success I have had is using the combination of UnBricable Resurrector + Odin.
Is there anything that the community might see that I'm missing?
I volunteer to be the ginnea pig for any additional crazy testing since at this point can't do much. If one or more developers want to work with me, we can develop a testing procedure and validate it.
Looking forward to make this Samsung Galaxy Player 5.0 device to work!
Best regards,
Well I tried to do the Odin flashing with a bootloader and pit, yesterday. They didn't work though, Odin said: FAIL, so my only simple option left was to wipe data and cache while in recovery mode. I did that and then rebooted and it worked, strangely enough. It was so simple...
But I had a soft-brick. I had to use oneclick.jar to un-soft-brick the device. Then I could use the power and volume buttons to get into downloading mode or recovery mode.
So maybe you should get into recovery mode and wipe all data and cache?
That's what I did anyway.
Good luck
I am an android noob and can't tell if it matters that much all I can sure say is that the us version isn't available as 16gig,only 8.
Sent from my YP-G70 using XDA
NullUser said:
I flashed with OnClickUnbrick which is part of Heimdall.
Did you unbrick your device already (and bring it to download mode)?
No - refer to here.
Yes -
You'll have to know if you have the US, International or EU version. FYI, The US version has a capacitive (non-physical) home button.
Install Odin
Make sure the Samsung Driver is installed (check device mgr)
Use a PIT from here
For the US version: Use this (2.3.5) or this (2.3.6), or this ROM (all ROMs are rooted)
For international use one of the ROMs here.
I'm just trying to help, I'm not resp. for any damage etc. etc. etc.
If you have a different device, or u need any other help, buzz me and will provide links, I have some, in just a few ago I didn't have a clue what a ROM means, so don't be shy to ask, and sorry if that's not the case.
And BTW, should u ever hear about a tested ICS ROM for the US ver. please PM or buzz me.
Click to expand...
Click to collapse
Have tried all of this, but still getting a black screen after Odin reboots the player. Odin is reporting "PASS!" though. Any ideas or suggestions?
If Odin says it's a Pass but it isn't showing anything on the screen, maybe it's a hardware problem? Do you have the Android SDK installed so you could try running the ADB to explore the device? If USB Debugging was enabled before your friend broke it, it might work. If that's the case, then it's a hardware problem and there probably isn't jack you can do about it. =\
What entropy said
Had this same thing happen to my galaxy player 5.0. just reconnected it then flashed the kernel again.
Will try installing the Android SDK
DeLaVicci said:
If Odin says it's a Pass but it isn't showing anything on the screen, maybe it's a hardware problem? Do you have the Android SDK installed so you could try running the ADB to explore the device? If USB Debugging was enabled before your friend broke it, it might work. If that's the case, then it's a hardware problem and there probably isn't jack you can do about it. =\
Click to expand...
Click to collapse
I'll install the SDK, is there a particular sequence of events or commands to execute once I have it installed?
Regards,
---------- Post added at 10:54 AM ---------- Previous post was at 10:47 AM ----------
Rapydax said:
Well I tried to do the Odin flashing with a bootloader and pit, yesterday. They didn't work though, Odin said: FAIL, so my only simple option left was to wipe data and cache while in recovery mode. I did that and then rebooted and it worked, strangely enough. It was so simple...
But I had a soft-brick. I had to use oneclick.jar to un-soft-brick the device. Then I could use the power and volume buttons to get into downloading mode or recovery mode.
So maybe you should get into recovery mode and wipe all data and cache?
That's what I did anyway.
Good luck
Click to expand...
Click to collapse
Forgot to mention that I also tried the oneClick unbrick software. I set the device in DownloadMode (via UnBrickable Resurrector) then I run the OneClick and click the button, the device then reboots and goes back to a blank screen, no reboot and still did not respond to any key pressing sequence.
Regards,
Forgot to mention that I also tried the oneClick unbrick software. I set the device in DownloadMode (via UnBrickable Resurrector) then I run the OneClick and click the button, the device then reboots and goes back to a blank screen, no reboot and still did not respond to any key pressing sequence.
Regards,[/QUOTE]
No, I meant that I had to use oneclick.jar to get back to downlaod screen, sorry for saying it wrong.
Once you're in download mode or recovery mode you should either restore your back-up files (recovery mode) or flash a new rom/kernel (download mode).
Some news...
I tried multiple combinations of :
- PIT
- Boot
- Kernel
- ROM (Kernel + FileSystem)
and at some point in time the device booted into CWM mode and it was sowing errors about not finding the following partitions:
/cache
/cache/recovery
/efs
/data
and other that couldn't read because they scroll in the screen.
I was able to save a copy of the log into the SDCard:
Starting recovery on Sun Jan 9 18:20:10 2005
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v5.0.2.7
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /efs rfs /dev/block/mmcblk0p10 (null)
2 /system ext4 /dev/block/mmcblk0p13 (null)
3 /datadata ext4 /dev/block/mmcblk0p14 (null)
4 /cache ext4 /dev/block/mmcblk0p15 (null)
5 /data ext4 /dev/block/mmcblk0p16 (null)
6 /emmc vfat /dev/block/mmcblk0p17 (null)
7 /sdcard vfat /dev/block/mmcblk1p1 (null)
8 /boot emmc /dev/block/mmcblk0p11 (null)
9 /recovery emmc /dev/block/mmcblk0p12 (null)
touch: /etc/mtab: No such file or directory
W:Unable to create /etc/fstab!
Irocessing arguments.
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
mount: mounting /dev/block/mmcblk0p15 on /cache failed: No such file or directory
W:failed to mount /dev/block/mmcblk0p15 (No such file or directory)
W:Can't unlink /cache/recovery/command
Does this look familiar to anyone? Any way to fix this?
Regards,
Orzmud, don't you have back-ups, so you can restore? If so, wipe all data and cache and then go to advanced and click on delete dalvik cache or something. Then restore.
I didn't have a back-up saved, so:
What I did when I got into downloading mode:
- Startup another computer and install Odin, the .pit files and the custom ROMs/kernels.
- Go into recovery mode.
- Wipe all data (3×), cache and dalvik (in advanced menu).
- Go back to downloading mode and connect to the pc.
- Open Odin 3 v1.85 and click on PDA. Select http://www.mediafire.com/?nch3g45zw5qdyhx (INTL). If you have the US version of the player then download the US stock ROM somewhere.
- Click on the "PIT" option and select one of the .pit files that fits your galaxy player version (http://forum.xda-developers.com/showthread.php?t=1389873)
- Then click on Start.
- Voila my player worked again.
I don't know if this will work for you, but it might be worth a try.
My phone is rooted using Kingoroot its was all running smooth until i update my phone now its stuck on boot logo i really need SWIPE KONNCET PLUS STOCK FIRMWARE Please help me please :crying: :crying:
Zaroonok said:
My phone is rooted using Kingoroot its was all running smooth until i update my phone now its stuck on boot logo i really need SWIPE KONNCET PLUS STOCK FIRMWARE Please help me please :crying: :crying:
Click to expand...
Click to collapse
What android version where you at and what did it upgrade to? Also, try booting into recovery and erasing all data.
i had tried everything i had wipe cache it and hard reset it too but still nothing work for me i just need a stock firmware of that mobile (Mobile name is swipe konnect plus ) and my phone android version is 5.1 lollipop please help me :crying:
what recovery is installed?
Need stock rom and custom recovery
Hey pls give me swipe konnect plus stock rom and custom recovery
aksthecount said:
Hey pls give me swipe konnect plus stock rom and custom recovery
Click to expand...
Click to collapse
That is unfortunately not how it works here...
swipe konnect plus error on inatalling cm12.1
I port a cm 12.1 for swipe konnect plus mt6580 when I flash cm with twrp 3.0.1 I am getting error like this.
Installing zip file '/sdcard/files/CyanoGenMod 12.1.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
/file_contexts: line 262 has invalid file type ubject_r:wmtWifi_device:s0/cache/dalvik-cache(/.*)?
|========================|
| CM12.1 r36 March BUILD |
| For Micromax A106 |
| BY MANAN VALLECHA |
| ---thanks from heart-- |
|Vijay , Ranjan , Vivek |
|Source - Rohan Taneja |
|========================|
minzip: Extracted 3 file(s)
could not detect filesystem for /dev/block/mmcblk0p5, assuming ext4
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
mount: failed to mount /dev/block/mmcblk0p5 at /system: Invalid argument
unmount of /system failed; no such volume
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
Creating filesystem with parameters:
Size: 262144
Block size: 4096
Blocks per group: 32768
Inodes per group: 16
Inode size: 256
Journal blocks: 1024
Label:
Transparent compression: none
Blocks: 64
Block groups: 1
Reserved block group size: 7
error: ext4_allocate_best_fit_partial: failed to allocate 973 blocks, out of space?
format: make_ext4fs failed (1) on /dev/block/mmcblk0p5could not detect filesystem for /dev/block/mmcblk0p5, assuming ext4
mount: failed to mount /dev/block/mmcblk0p5 at /system: Invalid argument
minzip: Extracted 1493 file(s)
ApplyParsedPerms: removexattr of /system/xposed.prop to 0 failed: Operation not supported on transport endpointscript aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '/sdcard/files/CyanoGenMod 12.1.zip'
What to do pls help me pls........pls.......
aksthecount said:
I port a cm 12.1 for swipe konnect plus mt6580 when I flash cm with twrp 3.0.1 I am getting error like this.
Installing zip file '/sdcard/files/CyanoGenMod 12.1.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
/file_contexts: line 262 has invalid file type ubject_r:wmtWifi_device:s0/cache/dalvik-cache(/.*)?
|========================|
| CM12.1 r36 March BUILD |
| For Micromax A106 |
| BY MANAN VALLECHA |
| ---thanks from heart-- |
|Vijay , Ranjan , Vivek |
|Source - Rohan Taneja |
|========================|
minzip: Extracted 3 file(s)
could not detect filesystem for /dev/block/mmcblk0p5, assuming ext4
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
mount: failed to mount /dev/block/mmcblk0p5 at /system: Invalid argument
unmount of /system failed; no such volume
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
Creating filesystem with parameters:
Size: 262144
Block size: 4096
Blocks per group: 32768
Inodes per group: 16
Inode size: 256
Journal blocks: 1024
Label:
Transparent compression: none
Blocks: 64
Block groups: 1
Reserved block group size: 7
error: ext4_allocate_best_fit_partial: failed to allocate 973 blocks, out of space?
format: make_ext4fs failed (1) on /dev/block/mmcblk0p5could not detect filesystem for /dev/block/mmcblk0p5, assuming ext4
mount: failed to mount /dev/block/mmcblk0p5 at /system: Invalid argument
minzip: Extracted 1493 file(s)
ApplyParsedPerms: removexattr of /system/xposed.prop to 0 failed: Operation not supported on transport endpointscript aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '/sdcard/files/CyanoGenMod 12.1.zip'
What to do pls help me pls........pls.......
Click to expand...
Click to collapse
What'd you use to port the ROM? Android kitchen or yourself? What kernel do you use?
I port it myself with XDA guide
I use custom ROM kernal 3.4.x and copy my kernal file uevent.tc and zimage file my kernal very is 3.10.72+
---------- Post added at 03:56 PM ---------- Previous post was at 03:53 PM ----------
It says unable to mount dev/block/mmcblk05/at system
---------- Post added at 04:01 PM ---------- Previous post was at 03:56 PM ----------
What does that mean
Hey, RAZERDAHACKER pls hlp me pls,pls,.......
Stock firmware for swipe konnect plus
aksthecount said:
Hey pls give me swipe konnect plus stock rom and custom recovery
Click to expand...
Click to collapse
Hello , if you really want the stock firmware then reply of this message . I will tell you where you can find the STOCK firmware for this device. But for sharing link of another Website i need permission from this XDA team. If they allow me then i can post here the link of the STOCK firmware.
Thank you .. and waiting for your reply.
sorry for late mess yaa give me the link
aksthecount said:
sorry for late mess yaa give me the link
Click to expand...
Click to collapse
tap on the quoted thread below to view the full answer
x.ak**** said:
like all my comments above to encourage me to help you.
Okay so first of all i will let you know why a phone gets bricked-
>corrupted rom
>some system files got deleted
>rooting
>modding
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
my case
i always keep two phones with me like one for my experiments and one as a backup. In this case i'll be talking about my lyf wind 3 that got bricked.
>actually i was trying to install twrp onto that phone but first i had to root it, and due to the upgraded android security, i wasn't able to do via kingoroot so i tried i-root and it did the job but instead of kingo-superuser i got some ****ty superuser so i tried granting permission to the actual superuser and while doing so i accidentally double rooted my phone (first with i-root and then with kingoroot), which was kinda stupid, so it just deleted some system files and my phone wouldn't boot after that. It just got stuck on the boot logo.
Click to expand...
Click to collapse
x.ak**** said:
tap on the quoted thread below to view the full answer
Click to expand...
Click to collapse
My case was that I flash cm 12 on my swipe konnect plus n was working fine but was reddish the common bug of cyanogenmod
and it can be fixed no matter how many I change file to clear bug so I just lost hope then I restore my stock via twrp n then the mobile was lagging to much so then I thought that it must be coz that twrp didn't restore my stock properly so search on Google swipe konnect plus firmware n I got the site on firmwarefile.com there was three stock room for swipe konnect plus so I download all of them n when I flash one of them it got brick then I flash another but sp flash tool giving me error "dram enable failed"
So I googled it n found that if we flash wrong preloader it hard brick your device that means the firmware for swipe konnect plus on the website r all wrong firmware n also check the build.prop of it was written the same model but I don't know what is happening I just want to abuse whoever upload swipe konnect plus firmware coz it brick my device pls if anyone is reading this pls pls pls pls help me to I just want preloader.bin file for my device if anyone anyone or your frnd is using swipe konnect plus pls pls pls pls contact me on my email [email protected]
---------- Post added at 09:29 PM ---------- Previous post was at 09:21 PM ----------
Zaroonok said:
My phone is rooted using Kingoroot its was all running smooth until i update my phone now its stuck on boot logo i really need SWIPE KONNCET PLUS STOCK FIRMWARE Please help me please :crying: :crying:
Click to expand...
Click to collapse
Hey do u still have swipe konnect plus reply me pls