Related
HI guys so i have been at this for a few hours now i was going to update my roms to 4.2.2
did a full backup and then did a wipe and the problem started the roms was not good so installation was aborted. when i connected the computer to phone after putting it in download mode so i could load stock roms and then load up back up the computer doe not recognize the phone.
THe CWM version 5.5.0.4 does not allow me to look at my sd card for some reason.... is my phone done?
so the backup was saved on teh phone thats why i moved it using file explorer to sd card ...
any way i can talk to my phone well make my computer talk to my phone.....i know it used to connect to me computer with no issues.
systemdude2 said:
HI guys so i have been at this for a few hours now i was going to update my roms to 4.2.2
did a full backup and then did a wipe and the problem started the roms was not good so installation was aborted. when i connected the computer to phone after putting it in download mode so i could load stock roms and then load up back up the computer doe not recognize the phone.
THe CWM version 5.5.0.4 does not allow me to look at my sd card for some reason.... is my phone done?
so the backup was saved on teh phone thats why i moved it using file explorer to sd card ...
any way i can talk to my phone well make my computer talk to my phone.....i know it used to connect to me computer with no issues.
Click to expand...
Click to collapse
Your recovery version is pretty old, considering cwm 6.0.3.6 is the newest...
So is there anyway to fix this ?
Download ROM Manager from the PlayStore and let it install the latest CWM, or download GooManager and have it install TWRP.
So far as the computer, you'll need to be more specific about 'talk to'.
Might need drivers, might need a new cable, can't tell from what you said.
I think if he wiped already he wont be able to download from the play store, if im reading the OP correctly, you already wiped the device, you flashed the 4.2.2 or 4.2 and it aborted..correct?
Step 1. Okay here's what you can do since the PC isnt reading your phone, reboot or restart your pc put phone in odin/download mode and see if it reads it now. If it does Odin a stock rooted rom, then get goomanger from the play store and install open script recovery which will give you the twrp recovery, then you can attempt the flash again of the 4.2 based rom.
Step 2. If it still isnt reading after a pc restart load your old rom on an sd card and try to flash the old tw rom with that older cwm recovery and see if you can get back at least to a tw rom. If that doesnt work then pull the battery out your phone let it sit for 2min, put the battery back in and get into odin/download mode, and see if pc recognizes the device and connection, if it doesnt, download kies and it might help with the connection issue.
Did that help bro. Let me know?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Op stated the he made a full backup. Should be able to boot directly into recovery and restore the backup?
thanks for the info everyone . the operating system is gone so no luck on play store.
mrkevo3000 yes the roms got aborted half way its weird why it would do that.... my phone has always had issues.
just like that as i am typing this my phone is now recognized by odin so i will what you said load up stock and the reflash my backup and then update cwm.
I will try and update and againg to 4.2.2 and let you know what happens.
I have seen so many flavors any preference one somethiong that might work on i747m ?
ill update this after recovering my phone and attempting reflash.
Also for some reason my sd card is not recognized by cwm and it is only looking at internal again never did this to me before thats why i got stuck.
Last time i attempted a update for some reason my apn settings were locked and could not be changed.
I did the same stupid thing myself. Really can not believe I did it but i was rushing and didn't read what it was, thinking i was doing something else. Was not worried as I had my trusty nandriod backup -.- . I guess I can consider myself lucky as i took it to telus hoping they would buy my story and they sent it to the samsung repair center. Worried all week that if they checked it would be clear i had voided the warranty and i would be paying a high repair cost or buying a new phone. Well I got the phone back an hour ago and they fixed it.... no charge. I guess I can consider myself very lucky.
systemdude2 said:
thanks for the info everyone . the operating system is gone so no luck on play store.
mrkevo3000 yes the roms got aborted half way its weird why it would do that.... my phone has always had issues.
just like that as i am typing this my phone is now recognized by odin so i will what you said load up stock and the reflash my backup and then update cwm.
I will try and update and againg to 4.2.2 and let you know what happens.
I have seen so many flavors any preference one somethiong that might work on i747m ?
ill update this after recovering my phone and attempting reflash.
Also for some reason my sd card is not recognized by cwm and it is only looking at internal again never did this to me before thats why i got stuck.
Last time i attempted a update for some reason my apn settings were locked and could not be changed.
Click to expand...
Click to collapse
I would use odin 1.85 and odin a rooted stock 4.1.2 rom.. then go to the playstore and download goomanger and get the teamwin recovery, by hitting menu inside goomanger app, and installing the open script recovery which will install the teamwin recovery, you can flash any pure google rom with that recovery, before you do make a nandroid of your current setup and then flash away, get into a habit of doing at least one back and check the md5 hash of the roms before you flash away... download using your pc instead of phone browsers, sometimes mobile browsers corrupt the files.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Please need help eMMc dump for i747 At&t s3
danvee said:
Download ROM Manager from the PlayStore and let it install the latest CWM, or download GooManager and have it install TWRP.
So far as the computer, you'll need to be more specific about 'talk to'.
Might need drivers, might need a new cable, can't tell from what you said.
Click to expand...
Click to collapse
Hello good morning i am in need of your help. I need a eMMC dump of a rooted AT&T sgh i747
Run this as root from a working SGH-i747:
Code:
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128
Please help me out really need the help. let me know if you can. Thank you for even reading my request.
Hey guys,
First off, I've searched far and wide for any help with my problem but it is such a peculiar situation that I have yet to find someone with a similar situation. I expect if I want to ever use my M8 again, I'll need to send it to HTC and pay a few hundred bucks to fix it. But maybe someone here will have an idea that I've missed.
Shortly after getting my M8, I unlocked my device, rooted it and installed a few roms. Everything was fine save for one major thing: no matter which PC I used (and I used MANY - 3 different windows destops, a windows desktop at the office and my Macbook Pro) the device was never able to mount and make the storage accessible. I knew at that point something at some point had gone wrong. I've long preferred to use a wireless file transfer app to send stuff to and from my phone so I wouldn't have to break out all my cables so I figured it wouldn't be a big deal. I'd make it work.
A few days ago, I decided to try a different rom than what I'd been using for months (HD Revolution - great rom!) and downloaded everything required. I booted to TWRP, wiped the usual stuff and flashed my rom. When I rebooted, I was continually met with a crash as soon as the phone started and was never able to get into the OS. No big deal - this has happened before with other devices, so I didn't sweat it. I simply powered down the phone and tried to get back to recovery. Here's where the problem really kicked in : when attempting to boot to recovery, my phone will bring up the Hboot screen but instantly try to select the first option, thus not allowing me to scroll down to "Recovery". No matter what I do, it brings up the white Hboot screen, automatically selects the first option, gives me some error (I'm at work so I don't have the device in front of me) and tries to boot to the OS. That takes us back to the automatic crash.
Now, I know usually the solution would involve USB and ADB, but like I mentioned at the start of my sad tale, connecting my phone to PC's results either in nothing (Mac) or a "the device has failed" message in Windows. I've tried removing all the phone drivers, reinstalling and using a few toolkit methods - the phone is just never ever detected.
So, that's it. I'm pretty much resigned to sending my phone in and the HTC folks quoted me about $200. I do have a functional phone at the moment so it isn't the worst situation in the world, but if I could fix this I'd be able to using it as my main device again or sell it for a good chunk of change - I just bought it in June.
Sorry for the long read!
As far as the storage issue, never seen that happen before so I'm not sure. When you plug it in to the computer does the phone ask if you want to connect it as a storage device etc?
The bootloader is a very peculiar problem. It almost sounds like you have an img file that its trying to read as soon as you boot into boot loader.
Try to install HTC sync. And make sure the computer has an internet connection when you plug it in via usb.
Try to flash stock recovery fw buddy
Maybe thats problem RUU
Cek mike blg to find all stock recovery fw
After that install custom recovery again
This sounds a little familiar.
In my experience I've found some firmware versions and ROMs very choppy.
I once had a problem with storage too, couldn't send anything over to my phone.
Fortunately I could access recovery, so used ADB sideload and installed another ROM. And went to another firmware and never looked back.
The last 401.6 firmware gave me all sorts of issue.
If you can access fastboot I'd also recommend new firmware 401.7 is working flawlessly for me with ARHD 21.
Sent from my HTC One_M8 using XDA Free mobile app
I would try putting one of the bootable ruus on your SD card so when it goes to your hboot, it'll read the RUU and install it
Awesome, some interesting suggestions here. Would I be able to somehow update the firmware via an SD card without any input from a computer? I managed to get into Recovery last night somehow (maybe letting the battery totally drain and charging it for a while did something) but plugging in my phone when in recovery still won't mount the storage or be recognized by ADB. Would I somehow be able update my firmware from recovery without the need of ADB'ing from my desktop? I've been looking at ROM threads and stuff and noticed that almost every rom requires new firmware or WiFI/radios other stuff won't work....
I'm at work right now so I'll definitely research this in depth when I get home, but if you guys could guide me in the right direction, I'd really appreciate it and maybe buy ya' a beer.
Xavierc123 said:
Awesome, some interesting suggestions here. Would I be able to somehow update the firmware via an SD card without any input from a computer? I managed to get into Recovery last night somehow (maybe letting the battery totally drain and charging it for a while did something) but plugging in my phone when in recovery still won't mount the storage or be recognized by ADB. Would I somehow be able update my firmware from recovery without the need of ADB'ing from my desktop? I've been looking at ROM threads and stuff and noticed that almost every rom requires new firmware or WiFI/radios other stuff won't work....
I'm at work right now so I'll definitely research this in depth when I get home, but if you guys could guide me in the right direction, I'd really appreciate it and maybe buy ya' a beer.
Click to expand...
Click to collapse
Download a rom that can use the 2.xx firmware. Look around and you should be able to find the roms. There's still plenty out there. Here's a little suggestion, reflash TWRP (or other recovery) through fastboot than grab a SD card and place the rom into the SD card and install the rom using through the use of a SD card. Just remember to do a full wipe before that
Before I say anything, I take full responsibility for my stupidity that resulted in a mistake that didn't have to happen.
Back in my SGS3 days I was pretty comfortable with flashing files and using adb. Besides using PurpleDrake to flash my LG G3, it's been a long while since I have tampered with a phone.
I was in the process of installing CloudyG3 when I remembered I forgot to perform a full backup but I didn't think too much of it, I thought everything would go smoothly but I was terribly wrong. It was as I started to flash CloudyG3's file that I realised it wouldn't work because I didn't download the file directly from my device onto my device. So here I am with an LG G3 that I've had for just over a month that cannot be used right now.
I have a stock firmware image on my computer so I'm hoping that I can push it to my device. The thing is I haven't used adb in so long to the point that I'm struggling to install Android SDK (asks me to locate something to do with java that I have installed, but I can't find it).
I'd greatly appreciate it if someone can guide me through the steps to get adb working and my phone back in working order.
Thanks in advance!
I have successfully managed to get the SDK tools working and I have been able to push CloudyG3 to my phone, it's currently uploaded but I doubt it'll work. I have a stock image that it in the KDZ format, is it safe to flash?
Edit: I done it! I don't know how, but I done it, no help is needed
Ok, so I have a Kindle Fire 2, running 10.5.1. About a year or so ago I bricked the board completely. I recently bought a replacement motherboard, but it said it can't be registered on Amazon, which it cant, (it cannot recognize any account information, new or existing). I have tried the root method found here http://forum.xda-developers.com/showthread.php?t=2075959 but the binary root method never does anything to the device, (it does at least recognize it), and Quemu can't seem to do anything successfully either. I'd like to just wipe the thing and put on a custom rom if it's possible, but if not, even returning to a working stock rom that I can register my account to would be ok. Anyone know what I can do to ge this thing back up an running again?
*Update*
Ok, I managed to get root, (I think), running option 3 in binarys root, followed by quemu, but I still cant get any apps running via Amazon, (Still can't register), nor does trying to side load apps work via adb.
So it seems most of my problems stemmed from using windows 8.1 to try and do most of the work I was doing via adb. I managed to get it rooted, although the root gives me very little usability. for whatever reason, this board is locked out of being able to register on Amazon, (not that I care all that much). I have been trying to load a new rom, via the instructions on this link, (after switching to Windows 7 to do the work), http://forum.xda-developers.com/showthread.php?t=2100963 Everything seems to have gone fine through fastboot, but when I try to load into TWRP, is just sits there saying its booting into TWRP, but never actually does so. Anyone know why, or what could cause this? I'd love to be able to load a working rom that has google apps access and make this thing useful again.
Got It...
So I eventually got TWRP to work, but I needed to use the 2.8.0.0 to do it, which is fine since I wanted to load a kit kat rom anyway. the only weird thing is that in order to use twrp, I have to go through the entire flashboot steps of loading twrp anytime I actually want to be able to successfully boot into twrp. I have no idea why this is, and although it is a pain in the rear, it still allowed me to, (after having to push the roms onto the device via adb since that was the only thing that would work), install PAC-Mans official 4.4 rom. I dont really need twrp anymore, so having to re-do the whole process to get into it doesn't make a difference. I am still kind of curious of what it is the place I bought the replacement board from did to it to cause so many problems, and why it could never register to amazon, but since I have a working kit kat tablet, I suppose it doesn't really matter. Still, if you are ever in the same pickle as I was, feel free to contact me and hopefully I can help you get through it.
I was needing a new phone and saw a Linus Tech Tips video where he took an LG G3 and put LineageOS on it. So I thought I'd try it out for myself following his guidelines at https://linustechtips.com/main/topic/1058206-lg-g3-lineageos-tutorial/
I bought an LG G3 D851 (T-Mobile version) off EBay for this. It's my first Android phone (yes, experimenting on my first Android Phone), I've always used Windows phones. This is what I've done to the LG G3 so far:
I reverted back to KitKat. Everything seemed to have gone just fine.
Then I downloaded the the Full Purple Drake Root and ran that after I figured out that .gz files are a compressed file and that can be decompressed. Everything seemed to have worked fine.
Then I downloaded the TWRP app on the phone and tried to backup the recovery via the TWRP app, which I'm not sure if it worked correctly. But anyhow.
Now that I'm writing this I see I missed this step:
number seven: Select the TWRP file we copied over earlier in the app, flash it to recovery, and then reboot to recovery
Click to expand...
Click to collapse
I guess I just didn't understand what was meant by flashing it over and has just copied it to the phone's memory which I later wiped.
Well then I went into TWRP recovery and tried to do a recovery backup, which it seemed to do just fine. I rebooted and tried copying it over to the computer, which seems to not have worked. I just have an empty folder on my computer as we speak.
Then back in the TWRP recovery, I selected Wipe>Advanced Wipe, and select Dalvik, Cache, Data, Internal Storage, and System – then swipe to wipe.
Then I downloaded the latest version and nightly of LineageOS zip file and the Opengapps zip file but then had a hard time figuring how to get them to the phone.
I figured out that I could stick them on an SD card and slip it into the LG G3 that I'm working on and could see the files from the TWRP recovery menu.
So I tried to install the LIneageOS zip file several times and it didn't work. I'm guessing it's because I forgot to flash a certain file to TWRP recovery and am not sure how to do that, especially now with the phone only booting into recovery mode with the TWRP menu since it's wiped clean and will just display the LG logo and turn the LED different colors if I try to normal boot the phone.
Well I still want to try to fix the phone and go for LineageOS. I spent nearly all night working on it so I may give it a rest for a few days. But any help or pointers would be greatly appreciated.
Now that I think about it, I didn't do what I mentioned ok #4 above about flashing the TWRP recovery because TWRP recovery was installed with the full Purple Drake root. However, the Linus Tech Tips instructions point to them rooting the phone with the lite version of Purple Drake (root only) and then flashing the newest version of TWRP recovery. So I wonder if my problem has to do with my having the latest version of TWRP recovery on my phone.
Ok. So I think I'm making progress, although that's just a feeling I have since I'm not suite what I'm really doing.
Anyhow the error code was something like "Unknown Error, Error Executing Updater Binary in Zip, Zip is for LG G3 D851, this phone is...(blank)". So I found an article in DroidThunder.com talking about this very problem. It suggested unzipping the rom on my computer and looking for the updater-script file and erasing some lines that apparently only have to do with verification. Then re-zip and retry.
Now I'm getting a "No MD5 file" message followed by an "Error flashing zip" message.
Edit: After reading this I take it I have an older version of TWRP, that is, v2.7.1.0, whereas the newet versio (for this phone?) is apparently 3.3.1-0. That seems to have an effect on this. I wonder if it's possibly to flash a newer version of TWRP onto this bricked phone. Anyhow, I'll have to look into that later. It's time to call it a day.
So recently I've been focusing on these two threads:
[GUIDE] LG G3 D851 Unbrick Qualcomm 9008 Fully Working... Unbrickable D851! by Omar-Avelar
And:
[GUIDE][FIX][DISCUSSION] LG G3 Hard Brick Recovery by l33tlinuxh4x0r
But I can't get either of them to work. I guess the only other thing would be to try to find a ROM, preferably the original KitKat that came with the phone, and hope and pray that I can get TWRP recovery v2.7 to install it.
I have the original as a tot file. But as far as I understand, I need a zip file that's set up for TWRP recovery.
Anyhow, trying to get this phone running hasn't been easy and has made other problems. Now every time I turn on my Surface 3 I have to go through BitLocker authentication. Hopefully turning bcd Test Signing off will stop that. But I'm getting to the point that I'm feeling like giving up.
Well that's it. Last night I found a zip file for the original Marshmallow ROM for my G3. I got it onto the SD card, went into TWRP recovery, saw it install, restarted and...
Now it's hard bricked. I cannot even get into TWRP recovery. The screen won't show a thing. I tried several times to get it into any mode possible, normal boot, TWRP recovery boot, download mode, and that jumping the pins trick, and I can't get it to where I can do something with the phone.
So I'm giving up on all this rooting, custom recoveries and custom ROM stuff. It all seems like a good idea, and I'd love to be a part of it all. But I take it this isn't for me. So I give up.
Thanks to all who have worked on this and have made the helpful forums about these phones! Maybe if I were more competent I would have figured it out.
Well, I said I was giving up. But maybe not. I did give up trying to recover the phone from being bricked and sent it out to a JTAG shop. For about $40 the phone is supposedly fixed and on it's way back.
But when it's back, do I just leave it alone this time, or should I try to get Lineage OS back on it again? Well, this is something that I haven't made my mind up yet. I see where I had made several mistakes when I first tried to get LineageOS on it. Maybe I know enough now that it won't happen again. But at the same time there's no guarantee that I won't me it up again, and have to pay some $40 again to have it unbricked.
SUCCESS!!!
So I got my phone back with stock Marshmallow working. Then I carefully went through every step on the Linus Tech Tips site, including installing the latest version of TWRP, and the next thing I know I'm running LineageOS 16 on my phone!
This is great! It's my first Android Phone and I've got it setup just about perfect! The only thing I kind of miss is Wi-Fi calling. But that didn't work so well on the Alcatel Window's phones I had anyway. But I got all the apps and most of the music I need installed and am ready to go! I also have two batteries, and the original isn't too bad, so I might carry that around as a backup until I'm sure how much battery I'll be using.
I'll be coming back and thanking all the ones who's posts and work have helped me individually. But if you read this and are one of those who have worked on TWRP, LineageOS and anything else that has helped me, Thank You!