I tried the new partition utility found in this section and I got an error from the sdcard portion, so it moved on to partitioning data but all it did was freeze and eventually I was stuck so I unplugged it. I managed to get back to TWRP and install the 6.2.1 update.zip but after I installed it I am stuck at the notorious "Your Kindle has detected a problem" screen and I can't get past it. I've tried KFU to boot into normal mode or even fastboot but I am stuck with the <waiting for device> message. I looked into it more and found this thread here:
http://forum.xda-developers.com/showthread.php?t=1414832
However, I can't get past the first command because I get this message:
exec '/system/bin/sh' failed: no such file or directory (2)
So I can't get anywhere without an error or waiting for device message, am I screwed or is there a way to fix this? ADB is working from what I can tell because reboot and similar commands work just fine, I think the partition just needs to be fixed. However when I click on Kindle properties in Device Manager I get 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"
}
Please help me guys, I don't want to have to send this thing back or have to get a factory cable.
I think you're screwed. Same thing happened to me. Had to send it back
Sent from my Galaxy Nexus using XDA App
I had the same issue and got it to boot by repartitioning it by hand and then installing the kindle 6.2.1 update. Now I am back up and running.
Did the same to mine earlier.
I followed the advice of Pokey9000 who referred to his thread.....
http://forum.xda-developers.com/showthread.php?t=1369405
You'll need to reflash at the end of this but it's defintely not bricked.
dnathan13 said:
I had the same issue and got it to boot by repartitioning it by hand and then installing the kindle 6.2.1 update. Now I am back up and running.
Click to expand...
Click to collapse
Can you explain how you did that?
The problem is that I can't get FFF or TWRP installed since I did a fresh install of 6.2.1.
Well nevermind guys I'm not gonna even bother with this. I contacted Amazon and I'm getting a new KF sent here in 2 days.
I also have a similar problem. I used TWRP to wipe everything and reflash the stock 6.2.1. Now I get the "exec '/system/bin/sh' failed: no such file or directory (2)" error. Everything I've found to fix the problem requires the shell and I can't use it. The Kindle never mounts in Windows either.
Those are the exact same issues I'm having. Oh well, I'm getting a new one and won't be messing with partitioning anymore.
The problem here is that you screwed your kindle and instead of doing the work to unscrew yourself you are sending it back to Amazon. All your doing is giving Amazon more reason to lock us out of the Kindle. They don't want to be taking back equipment that you ruined.
It's because of this kind of stuff that we are constantly fighting to get root on our devices. If you root your device and soft brick it you shouldn't send it back to the manufacturer. Do us all a favor and when you get your new KF, do not root it.
This is why company's hate root. If you cant take the time to fix your kindle after you f*** something up then don't root it.
edit: haha same post above me
I like how you guys say that when there is no real solution to solve this problem.
I got my new KF a day early. I sure won't be messing with partitioning again.
how do you partition by hand
There is a way, people have come back from completely wiping out the partition table on their kindle, I just can't find the post on how they did it. If you look in the custom kernel thread awhile back, the kernel had a glitch and caused some kindles to wipe out all partitions. So you can come back from it, just it hasn't happened to many people.
Edit: I believe you could have made it back using some form of this guide. http://forum.xda-developers.com/showthread.php?t=1388996&highlight=partition , but I'm not well versed enough in doing all this crap.
Edit again: If theres no real solution then you should be SOL, its not amazons fault you messed something up so badly on your kindle its unrecoverable. So yes, I will say that even if there is no solution.
Matt V said:
Well nevermind guys I'm not gonna even bother with this. I contacted Amazon and I'm getting a new KF sent here in 2 days.
Click to expand...
Click to collapse
Wow, you suck at life. Thanks for being part of the reason people want to stop us rooting. You have no idea what you are doing so you send it back and make amazon eat it. You didn't even try to fix it.
Related
I got the root, took 5 minutes but anything after that, not so good.
I spent all day trying to root, nand, flash and am left with nothing but frustration. I had problems with htc sync, still do. Clockwork recovery won't flash and I can't flash a rom from the sd card or usb cable.
I like to tinker but it just doesn't seem worth it. jailbreaking my iphone was a cinch compared to this. I'm very frustrated because I was looking forward to what a custom rom could provide and to getting froyo early.
Thinking of going back to stock and trying the unrevoked method (can I just apply the unrevoked method or do I have to revert back to stock and then try it?) and if that doesn't work just stick with the root.
What method are you using? What errors or problems are you running into? You need to provide more details in order for anyone to be able to help you. Rooting the Evo and nand unlocking has never been easier (unless you are running the latest OTA).
Edit: You don't need to post multiple threads for the same issue. If you're not get any replies, it's most likely because you didn't provide enough info.
yeah i been trying to get that clockwork to install too i cant find a zip for it or anything. I am rooted but still dont have any idea how to enable su to use the rom manager app. i tried that idiot proof which is missing the link for clockwork. I also tried the the simple root but when i hit the exe i get a error. i had almost no issues with the hero i been trying for all day too. I am amazed no one else had another link for that clockwork recovery.zip i woulda been done hours ago. very very frustrating but i am sure its my own fault for being a nubbbbb lol. sucks too cause i work all weekend and i wanted to get this done on my day offf.. which was today
you don't flash recovery using a zip. You need to flash the img. I just checked the clockwork thread, the links do appear to be down. Use Amon_RA
Doesn't get any easier than this: http://forum.xda-developers.com/showthread.php?t=706411
lgevo said:
yeah i been trying to get that clockwork to install too i cant find a zip for it or anything. I am rooted but still dont have any idea how to enable su to use the rom manager app. i tried that idiot proof which is missing the link for clockwork. I also tried the the simple root but when i hit the exe i get a error. i had almost no issues with the hero i been trying for all day too. I am amazed no one else had another link for that clockwork recovery.zip i woulda been done hours ago. very very frustrating but i am sure its my own fault for being a nubbbbb lol. sucks too cause i work all weekend and i wanted to get this done on my day offf.. which was today
Click to expand...
Click to collapse
Go here
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
About half way down the page you'll see a list of phones, click the EVO. Clockwork recovery will begin downloading.
imo don't use clockwork, people have been reporting problems with wiping with it.
Where does the recovery clockwork img go?
jgarozzo said:
Where does the recovery clockwork img go?
Click to expand...
Click to collapse
Have you read any guides or tutorials?
http://forum.xda-developers.com/showpost.php?p=6806125&postcount=1
mrono said:
imo don't use clockwork, people have been reporting problems with wiping with it.
Click to expand...
Click to collapse
He can use clockwork, i dont think he will need to wipe the SD, i mean, is not really necesary
,is it?
mikevillarroel said:
He can use clockwork, i dont think he will need to wipe the SD, i mean, is not really necesary
,is it?
Click to expand...
Click to collapse
It is if you had apps2sd stuff on it from another rom. That's where I ran into problems. I've seen other threads where people reported it not wiping cache correctly. I never saw that personally though.
Here...maybe this will help
{
"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"
}
redrazr7791 said:
Here...maybe this will help
Click to expand...
Click to collapse
Hahahahaha
Hi all,
Here's short history of the phone:
Friend of mine drop his on the concrete about June of last year and whole screen was cracked (not pretty). About month ago I found LCD Screen with Digitizer on ebay bought it and replaced it.
After turning it on everything was working except random reboots. Phone was not registered to any account so there was no internet only WI-FI.
So I started going into system updates and downloading HTC updates it did two of them and I think on the 3rd one it just starts to boot white HTC EVO 4G screen comes on and then it reboots.
Only pulling the battery will stop it.
This is all on stock HTC Sense ROM, rooting was never attempted!
I've searched thru the forums here but everything here relates to failed rooting process.
Can someone please make any suggestions?
Bellow is the pictures of boot loader.
Help is greatly appreciated!
{
"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"
}
These directions are for un-rooting, but should fix your phone:
http://forum.androidcentral.com/htc...19278-how-unroot-return-stock-ruu-method.html
Fazulka said:
These directions are for un-rooting, but should fix your phone:
http://forum.androidcentral.com/htc...19278-how-unroot-return-stock-ruu-method.html
Click to expand...
Click to collapse
Thank you!
Followed the instruction, run RUU and it starts to check the phone after this I get error[170]: USB connection error.
I've tried over 10 times.
Step 4 says "Make sure USB debugging is enabled on your phone."
I can't even log into Sense?
The only other thing you can do is find a PC36IMG.zip and put it on your microSD card, then reboot into the bootloader. It should find it and reflash everything, the same as using the RUU.
ffolkes said:
The only other thing you can do is find a PC36IMG.zip and put it on your microSD card, then reboot into the bootloader. It should find it and reflash everything, the same as using the RUU.
Click to expand...
Click to collapse
I've tried using this method found here
I placed PC36IMG.zip in root of the SD card. But when I boot into recovery I can see for about 3 seconds on the right side status bar how it checks PC36IMG.zip file but then it goes back to recovery. It never ask me if I want to update like it says in the above tutorial "Do you want to start update?"
Any other suggestions?
JohnnyBeGood113 said:
I've tried using this method found here
I placed PC36IMG.zip in root of the SD card. But when I boot into recovery I can see for about 3 seconds on the right side status bar how it checks PC36IMG.zip file but then it goes back to recovery. It never ask me if I want to update like it says in the above tutorial "Do you want to start update?"
Any other suggestions?
Click to expand...
Click to collapse
I had to unroot mine and I found that u have to have the right pc36img file. If you dont know what ver rom was running then you may need to try them all. But I had the same problem it just wouldent install the file. Keep trying and if you need help finding them Ill help ya.
I found this but its not the same place I got mine from. http://www.filecrop.com/htc-evo-4g-roms.html
Thanks for the reply!
Somewhat of a progress. I tried countless times and it always gives me USB connection error: Then I downloaded HTC Sync and and I think I went to Hboot and I heard sound on windows it seemed like phone got recognized and I was able to finish the processes. It was flashed using RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed. Then when I went to again in recovery it was again red triangle over the phone.
After that I just let it try to boot and it finally booted into HTC sense!
Turned on WI-FI and wanted to check if there's any updates and it said no updates?
This is what recoveries I've tried so far:
Amon RA 2.1.1
Amon RA 2.2.1
Amon RA 2.3 (Added 02/09/2011)
Stock Recovery 3.26.651.6 (Added 01/18/2011)
Stock Recovery 3.29.651.5 (Added 01/18/2011)
Stock Recovery 3.30.651.3 (Added 01/18/2011)
Stock Recovery 3.70.651.1 (Added 01/18/2011)
One by one I tried each one renaming to PC36IMG.zip and none of them asked me if I want to do the update. It just checks it and goes back to bootloader.
Why do I get red triangle?
What should I do now?
Help is appreciated!
My wife got me a brand new A500 off ebay a couple of months ago for a Christmas gift(for me it's only three days old). So far I love it but it will not take the OTA update that it keeps bugging me about. The download starts fine but then stalls out mid download. I looked here http://forum.xda-developers.com/showthread.php?t=1113878 but did not see my current version there. Can anyone point me in the direction of the OTA I need to download and flash with recovery? My build is Acer_a500_1.145.09_com_gen1 I'm running 3.0.1. It looks like it's trying to download 4.010.11.
Further info:
According to the log the file name is Acer_A500_1.145.09_4.010.11_com_gen1_1311243587838_bd1ab95c.zip
I can't find that file anywhere on the net.
The reason I would suspect is because someone replaced the stock recovery? Off eBay you say, was it brand new and never used? It sounds like it was used or someone tampered with it?
If that's not the case, then you can just install the update manually. Download the update you want and put it on your external SDCard and then enter recovery (using power and volume). The recovery will install the update for you.
timmyDean said:
The reason I would suspect is because someone replaced the stock recovery? Off eBay you say, was it brand new and never used? It sounds like it was used or someone tampered with it?
Click to expand...
Click to collapse
It said it was brand new. My wife would not buy something like this used. The weird thing is it knows it has an update and it starts to download and get's up to half way downloaded and then it just stops. It shows that it still is pulling data but the downloaded file size doesn't increase anymore after it stalls.
Ive been looking into rooting it and since I'm on 3.0.1 it appears Gingerbreak is all I need. The next question is what rom should I get and how do I go about installing it? I've never rooted droid before and most instructions on XDA are written for the experienced level and not the new guy. I'd like to stay fairly stock but rooted.
Sent from my A500 using Tapatalk
There are reports of others having the same issue. They say that a soft reset often fixes it.
You can use my tool to flash in 3.2.1 which is rooted. http://forum.xda-developers.com/showthread.php?t=1307539&page=14
timmyDean said:
There are reports of others having the same issue. They say that a soft reset often fixes it.
You can use my tool to flash in 3.2.1 which is rooted. http://forum.xda-developers.com/showthread.php?t=1307539&page=14
Click to expand...
Click to collapse
Just to make sure I'm getting it right: I go here http://forum.xda-developers.com/showthread.php?p=20680452 download that to my PC and follow the instructions contained within and I end up with a stock rooted 3.2.1? I don't need to download anything else right? A soft reset for this tab is pusing the little red button on the end by the USB port?
Sent from my A500 using Tapatalk
Yes, if you want to flash 3.2.1 stock with root read the instructions in the download. The download has everything in it.
The soft reset everyone talks about is using the paperclip in that little hole next to the USB port.
timmyDean said:
Yes, if you want to flash 3.2.1 stock with root read the instructions in the download. The download has everything in it.
The soft reset everyone talks about is using the paperclip in that little hole next to the USB port.
Click to expand...
Click to collapse
Sweet. You're a life saver. Thanks for translating it all to noob for me. Will I need to reinstall all of my apps and such afterwards?
Sent from my A500 using Tapatalk
Yes, the flashing tool makes it just like new, out of the box, but with root.
timmyDean said:
Yes, the flashing tool makes it just like new, out of the box, but with root.
Click to expand...
Click to collapse
OK that's not a big deal. The SD card will remain intact though right?
Sent from my A500 using Tapatalk
Jds method does work. But you can also trybthis.
http://forum.xda-developers.com/showthread.php?t=1410802
Simple easy no computer needed
timmyDean said:
Yes, the flashing tool makes it just like new, out of the box, but with root.
Click to expand...
Click to collapse
I tried your method and I get stuck at the serial number part. It says ADB server out of date. What do I do?
{
"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"
}
Edit: Never mind. I got my steps out of order. I was clicking next before running test.cmd
Last edit: It appears to have worked. I'm back to the initial setup screens just like when I first got it.
{
"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"
}
Motorola Defy XT: So what does it mean when this is the only screen your rooted Defy XT can make??? Once i turn it on this the first and only thing that appears on the screen but after a few min. my phone starts being a phone and everything, well at least making all the sounds it used to and receiving messages still, but the screen is kaput. Is my phone Bricked for good? or is there anything I can do? Please someone help!!! :crying:
Did this happen after rooting or anything else
If you have cwm then find your rom And flash it
If you don't have cwm and you have enabled USB debugging then flash it via adb
If you are able to get in recovery mode then your phone is not bricked. It's just a system crash
Did you flash any zip from pimp my rom then flash the rescue package
By the way just stay cool. It will only take not more than a week or two to know the cause and repair it
Sent from my A11 using xda app-developers app
arnabbiswasalsodeep said:
Did this happen after rooting or anything else
If you have cwm then find your rom And flash it
If you don't have cwm and you have enabled USB debugging then flash it via adb
If you are able to get in recovery mode then your phone is not bricked. It's just a system crash
Did you flash any zip from pimp my rom then flash the rescue package
By the way just stay cool. It will only take not more than a week or two to know the cause and repair it
Sent from my A11 using xda app-developers app
Click to expand...
Click to collapse
Hey thanks for the response!
I've actually only just rooted my phone. I haven't put any rom on it. It is still running the factory gb on it. Only rooted it so that I could run a screen shot app on it, and was probably eventually going to rom it once I became a little more knowledgeable about doing so. But everything was working fine with the phone after rooting it, for about 2 weeks even, but yesterday I just pulled out my pocket after coming out of the grocery store, clicked it to unlock it and there was that screen. Tried everything to get rid of it, took the battery out, plugged it in the wall, my computer. Nothing. Weird thing is though, after 5 min of being on, it will continue being the phone that it is, making all its regular sounds and receiving messages and notifications, just with that pixelated screen, which leads me to believe that it might be a hardware/bios problem, or if phones even have bios. This is my first smart phone so I'm just really starting to get to know it. Again, appreciate all help given! Just bummed this phone I've had for a month has already crashed on me.
arnabbiswasalsodeep said:
Did this happen after rooting or anything else
If you have cwm then find your rom And flash it
If you don't have cwm and you have enabled USB debugging then flash it via adb
If you are able to get in recovery mode then your phone is not bricked. It's just a system crash
Did you flash any zip from pimp my rom then flash the rescue package
By the way just stay cool. It will only take not more than a week or two to know the cause and repair it
Sent from my A11 using xda app-developers app
Click to expand...
Click to collapse
Also forgot to mention I tried a factory reset by memory but with no visual it's hard to see if I'm even doing anything.
Search for your stock from and flash it
You can also use the custom from like miui v5 for defy/defy+ http://forum.xda-developers.com/showthread.php?t=2232947
Do you have a cwm recovery? Or you have to use the fastboot method
Sent from my A11 using xda app-developers app
So, pretty much a long time lurker and much lover of this site. I do quite a few roots on various devices for my job (computer forensics) and I've rooted a Galaxy S8 and its stuck on the Samsung boot logo and I desperately need to get it out without wiping the data on it!
The annoying part, is I did this a few days earlier to a test S8, all the same apart from the build number and it was bloody flawless. I got root access. Did it to another device and it crapped out.
I used cfar_samsung_sm-g950f_dreamltexx_nrd90m.g950fxxu1aqi7_adt0.zip direct from firmware.mobi (for both devices - first was obviosuly a different build number).
I'm in a bit of a panic mode at the moment. I tried this:
https://forum.xda-developers.com/v20/how-to/how-to-fix-twrp-bootloop-t3513580
After attempting root on my replacement phone, I could NOT boot to system. Each time I rebooted to "System", it would boot straight to TWRP over and over. I tried reflashing stock files. No verity patching.. etc.
The Fix:
Download the latest version of TWRP specific to your device here https://build.nethunter.com/test-builds/twrp/lge/
Flash the file and the device should now be able to boot to system. If that doesn't work try another version.
I spoke to @jcadduono about my problems and he believes there may have been something weird going on in the misc partition. Reflashing TWRP will/should fix the problem.
Thanks @jcadduono for all the support.
Click to expand...
Click to collapse
But it did not work. I can get into TWRP Recovery with it (and into Download mode) but TWRP wont kick it out of the boot loader issue. I've tried installing super user and all sorts, but I can't mount Data to actually achieve anything?
Please, any help is much appreciated. If there is anything obvious I'm missing please tell me.
Thanks,
DG.
First of all, I would like to ask for mod/s to have this move to proper thread section.
What is the exact model of your S8?
What is your TWRP version you installed?
@DanGlee
Can you show us the picture of twrp error you get?
You mentioned this
"but I can't mount Data to actually achieve anything?"
Can you send us the exact error of twrp and post it in here? It could be that data partition is corrupted, and if it is, then there's no way we could get your data back.
But if you can get /data partition mounted, then you could make a backup in twrp and reflash everything to stock.
Apologies for not posting this in the correct place. It's a minefield of threads.
I don't have the phone infront of me at the no, bit will do it first thing in the morning.
Thanks.
you cannot mount data if you don't FORMAT DATA first
batuzai04123 said:
First of all, I would like to ask for mod/s to have this move to proper thread section.
...
Click to expand...
Click to collapse
DanGlee said:
Apologies for not posting this in the correct place. It's a minefield of threads.
...
Click to expand...
Click to collapse
Thread moved :good:
Wood Man
Forum Moderator
manups4e said:
you cannot mount data if you don't FORMAT DATA first
Click to expand...
Click to collapse
Yes , forgot about that.
If data mounted is inaccessible, your only option is to format data partition, which sadly, erase all your data from your phone.
Sorry @DanGlee you won't be able to retrieve your data anymore.
Thanks for the replies.
Its definitely not sounding good.
As an update as promised anyway, here are some details requested.
Its an Galaxy S8 SM-950F (UK) with Build Version ending ...AQI7
(Running Android 7)
I've put TWRP 3.1.0-1 on it.
I can't really see any error codes or anything, but here are some images of it failing to install SuperUser.
{
"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"
}
Thanks for the responses. You guys genuinely are helpful and if you say its FUBAR then I trust your diagnosis. (I think I was just clutching at straws that I might be able to salvage something!)
Thanks,
DG.
Edit, I can't upload images. XDA is being an arse. I just want to put in this link [insert_https_here]://imgur.com/gallery/Teceb
DanGlee said:
Thanks for the replies.
Its definitely not sounding good.
As an update as promised anyway, here are some details requested.
Its an Galaxy S8 SM-950F (UK) with Build Version ending ...AQI7
(Running Android 7)
I've put TWRP 3.1.0-1 on it.
I can't really see any error codes or anything, but here are some images of it failing to install SuperUser.
Thanks for the responses. You guys genuinely are helpful and if you say its FUBAR then I trust your diagnosis. (I think I was just clutching at straws that I might be able to salvage something!)
Thanks,
DG.
Edit, I can't upload images. XDA is being an arse. I just want to put in this link [insert_https_here]://imgur.com/gallery/Teceb
Click to expand...
Click to collapse
Unlucky i don't think you can recover your file. I took a look and didn't find anything. Please pay attention at what you do when rooting or doing anything to your phone. First you need to see all the steps to avoid problems like this!
If can help i used this very simple guide to root my phone [YOUTUBE]https://www.youtube.com/watch?v=L_lsVsbujYg
[/YOUTUBE]