Hi guys!
I rooted my tf101 2 days ago because a would like to run gameloft games.
Everybody sad that i need to replace the product.model for example to A500 or GT-P1000 or XOOM. But it hasnt worked. So i replaced the full build.prop to the Xoom's, and the transformer hasnt started since then. Its just loading the grey Asus logo forever. I dont know what should i do, please help !!!!!!!!!!!
Did you do a nandroid backup?
Did you save a copy of the build.prop? If you did, use ADB to push it back to your tablet
oááá
Yes i saved the original build.prop, but into the tablet's download folder. So i cant get it. A tried to hard reset but it stops at the same point (the grey asus logo).
And how should i get a new build.prop?
windows
and windows does not support it because the tablet can turn on
See if you can ADB pull the build.prop or see if someone can post one (are you on stock ROM?).
You could also try manually flash the latest firmware from ASUS
how
baseballfanz said:
See if you can ADB pull the build.prop or see if someone can post one (are you on stock ROM?).
You could also try manually flash the latest firmware from ASUS
Click to expand...
Click to collapse
Ok but how if the pc(windows) doesnt recognize it?
danis2142 said:
So i replaced the full build.prop to the Xoom's, and the transformer hasnt started since then. Its just loading the grey Asus logo forever. I dont know what should i do, please help !!!!!!!!!!!
Click to expand...
Click to collapse
Seriously? You did that just to play some games?
Sorry but you kinda deserve what happened.
So?
So, can you/anyone tell me what i have to do ??
I have no idea how i could contact with the devices which dont turn on and cant be recognized by windows
Here are your options. Try in this order. Look up and properly research how to do each solution.
1. Adb
2. Download firmware from Asus and flash.
3. Nvflash
4. RMA
horndroid said:
Here are your options. Try in this order. Look up and properly research how to do each solution.
1. Adb
2. Download firmware from Asus and flash.
3. Nvflash
4. RMA
Click to expand...
Click to collapse
At this point #2 seems like a good idea.
http://forum.xda-developers.com/showthread.php?t=1587593
If not try setting up ADB somehow. In certain situation ADB can still work even on the stuck Eee Pad screen.
Post your serial # to see if it's NVFlash compatible.
If all above failed, RMA.
RMA
Guys, thanks a lot for the help, but all failed. I have tried everything u have said but fail.
Now I am at RMA, only one more question: I pressed Power and Volume down buttons, and set hard reset. The questions is that did it delete the root, so wont asus recognize that i rooted it ?
Thanks and RMA
baseballfanz said:
At this point #2 seems like a good idea.
http://forum.xda-developers.com/showthread.php?t=1587593
If not try setting up ADB somehow. In certain situation ADB can still work even on the stuck Eee Pad screen.
Post your serial # to see if it's NVFlash compatible.
If all above failed, RMA.
Click to expand...
Click to collapse
Guys, thanks a lot for the help, but all failed. I have tried everything u have said but fail.
Now I am at RMA, only one more question: I pressed Power and Volume down buttons, and set hard reset. The questions is that did it delete the root, so wont asus recognize that i rooted it ?
A factory reset only delete users data. It doesn't alter the os in anyway. If your tf is stuck there's no way for Asus to tell of it's been rooted. They'll probably just flash the latest OS onto it.
Feeling happy
baseballfanz said:
A factory reset only delete users data. It doesn't alter the os in anyway. If your tf is stuck there's no way for Asus to tell of it's been rooted. They'll probably just flash the latest OS onto it.
Click to expand...
Click to collapse
Its the happiest news of this (anywhere) suck day
and are you sure about that i wont lose my warrant?
You never posted your serial#. Could be a slight chance you have an SBK v1 which you can NVFLash
To play gameloft games all you need to do is some googling and look on a thread with confirmed gameloft working on tf101
.....change model was probly more of changing the model on gameloft website. No wonder google is trying to block the exploits.
THIS. Is why you shoulden't root. Wth man why would mess around with stuff like that.
Sent from my Transformer TF101 using Tapatalk
Related
Ok so I just tried to get the 3.1 update from the XOOM pushed to my tablet and well it bricked me so dont try this if a few people r wanting this just wait for the 3.1 update later this year.
ouch, so what are you gonna do now, can u fix it?
dc13 said:
Ok so I just tried to get the 3.1 update from the XOOM pushed to my tablet and well it bricked me so dont try this if a few people r wanting this just wait for the 3.1 update later this year.
Click to expand...
Click to collapse
Can you tell us where you get the update file? Can you share it?
Also, how you flash the file? Through recovery?
Can you describe the 'brick' situation? Boot loop?
Finally, how are you going to restore back to original?
Thanks a lot.
He should be able to nvflash back I'd think.
muqali said:
He should be able to nvflash back I'd think.
Click to expand...
Click to collapse
nvflash isn't working for us atm
I think that he can use a stock update.zip and flash it through recovery.
ardatdat said:
Can you tell us where you get the update file? Can you share it?
Also, how you flash the file? Through recovery?
Can you describe the 'brick' situation? Boot loop?
Finally, how are you going to restore back to original?
Thanks a lot.
Click to expand...
Click to collapse
No I'm not going to share a update that will brick ur tablet.
Boot look at the Android. I know Im bricked.
I'm just going to return it and get my money back and ill wait a little bit.
There is NO NVFlash
I can use the Chinese update.zip but id rather not
dc13 said:
No I'm not going to share a update that will brick ur tablet.
Boot look at the Android. I know Im bricked.
I'm just going to return it and get my money back and ill wait a little bit.
There is NO NVFlash
I can use the Chinese update.zip but id rather not
Click to expand...
Click to collapse
You could flash the chinese thing.. try to flash my recovery and if it doesn't work just use dd to flash the recovery from china again
seraphimserapis said:
nvflash isn't working for us atm
Click to expand...
Click to collapse
Hadn't been following our support too closely. I just assumed it worked on all tegra tabs equally. God what I wouldn't give for tabs to be like PCs.
Use the chinese update.zip
Its not bad... I had to use it because I was fooling around too much and crashed with no reboot in sight. I used SYSTEMAPP REMOVER to disable all the chinese apps and root explorer to delete the old files in /system/app then rebooted.
Also, you can add the marketplace through the /system/app just enable read/write and there is no need to push through ADB!!! it will give you error once, rewrite over the files again, re-install, and re-start and voila... you get the free games from the "GoMarketHD" and you get the MARKET back, granted, its not the HONEYCOMB market but hey, its the market... jejeje
The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).
drk.hd said:
The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).
Click to expand...
Click to collapse
There is a way to do this with adb... I just do not know the proper commands. Sorry
Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.
sengwall said:
Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.
Click to expand...
Click to collapse
No, I don't think it does, but I'd rather not take the chance.
drk.hd said:
No, I don't think it does, but I'd rather not take the chance.
Click to expand...
Click to collapse
YES! It absolutely does. The second the device was rooted it broke warranty.
Sent from my myTouch_4G_Slide using XDA App
The same thing actually happened to me earlier today. I was just browsing some sites on the ICS rom when it just stopped responding. I couldn't get it to recognize any touches even after a bunch of reboots, so I just figured it to be some bug that hadn't been squashed yet. When I dropped down to recovery and saw the same issue, I knew I had a real problem.
Hoping against hope, I tried both CWMR and TWRP on it and got no results. Like you, I figured it would have to go back to Amazon, so I started searching for a way to get it back to stock... nothing obvious jumped out at me because everything is written with access to recovery in mind... which doesn't help.
So, I started reading about adb and going through the built-in help. As I was familiarizing myself with some basic adb commands and options, I left TWRP open in front of me. I don't know how long I had it that way when I mindlessly tapped on the screen and thought I saw it flicker. Yes! I had pressed the Wipe button and it had taken me to that section. It's been working fine ever since.
I'm not claiming I did anything and I don't have a how-to on how to fix it, but it couldn't hurt to just leave the thing running in recovery for a while and see if the touchscreen comes back to life for you too.
Still, I'd love to see someone with more adb knowledge provide a simple tutorial on how to get it back to stock without access to recovery. I'm sure it would be helpful to someone in the future... maybe even me if the same problem comes up again.
Best of luck to you.
Just ignore my comment
Sent from my Amazon Kindle Fire using Tapatalk
If your on the rooted stock rom you could always wait until Amazon pushing the next OTA
You will have to make a fastboot image and flash that with fastboot. But before you create the image, you will have to create all the appropriate symlinks. Then you run...
Code:
make_ext4fs -l 512m -a system -s /path/to/fastboot_system.img /path/to/system_folder
That will create the fastboot image. Then when FFF gives you fastboot access, you run...
Code:
fastboot flash system fastboot_system.img
You will also need a fastboot image for recovery and the bootloader.
Isn't there any easy way like with my desire, simple ruu.
Or hasn't anyone created these images to flash. I also need to get back to stock everything and send it to amazon, my wifi gets error after some period of time and some times when screen goes off, try'd 3 roms and stock.
There is a way to tell the device to install /sdcard/update.zip via shell commands. I forget what they are tho. Something about the extendedcommands. If I have time tomorrow I'll look it up.
here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
b63 said:
here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
Click to expand...
Click to collapse
Thanks for the link. I'm back on this thread because I think my Kindle Fire touchscreen is now dead for good. However, those instructions do not work as-is because you need to press a button on the screen to tell the Kindle Fire to allow the host to mount it as a USB Mass Storage device. Although those instructions don't get you all the way there, I was able to use the core idea to get my Kindle Fire back to stock. So, many thanks for pointing me in the right direction.
On top of the touchscreen not working, I ended up partially bricking the device trying to find a way to flash it back to stock, so I had also posted in the Unbricking thread. I posted my solution there....
http://forum.xda-developers.com/showpost.php?p=23226260&postcount=701
Odds are, if you have a device that is booting correctly, you will be able to ignore steps 3 and 4 and get it booting back to stock. I do have a couple of other suggestions... Leave your USB cable hooked up to the Kindle Fire as it boots into stock for the first time. This is the only time that it will automatically mount the /sdcard to your computer and you will have a chance to reclaim (and delete) all the files stored there. You can also do something like 'adb pull /sdcard C:\sdcard' before you flash. Also, depending on what ROM and apps you were using before starting the process, you might want to delete your user data and reset the device to factory defaults. You can do this with 'fastboot erase userdata' and the next time you start the device, you'll get a warning that it's about to reset. Hit the power button and you should have a clean, fresh from the factory Kindle fire... albeit with a broken touchscreen. Good luck!
After several failed attempts to follow this guide (no offense to posters; I appreciate your contributions), I found this to be the simplest method.
http://stackoverflow.com/questions/10817721/wipe-data-factory-reset-through-adb
Download stock update, then it's basic procedure in adb:
adb push C:/update.zip /sdcard/update.zip
adb shell
recovery --wipe_data
After reboot, go back into to adb shell and do "recovery--update_package=/sdcard/update.zip"
Factory reset, etc. and you're good to go.
Okay... so the other day in class I was thumbing through the intrawebs and noticed the leaked ICS had came out for the A500... I tried flashing the ROM to my tablet, thinking it would be a cinch if I just followed the directions. No go, just stuck on Android boot logo. That's fine and all, made a back up with CWM (which i think was my initial problem with the ICS version.. correct if I'm wrong please,) but... my back-ups check sums were mismatching for everything. Couldn't get them to match and couldn't figure it out so I decided to just flash root stock version back on to the tablet and go from there using my titanium backup.
I flashed, and bam... vibrating black screen, no CWM recovery anymore no matter what I do. I've been using the SDK manager / ADB terminal thinger / EUUS Acer Iconia Tab Software Upgrade Utility. I cannot for the life of me find my CPUID, or at least the RIGHT CPUID. I understand to use software to find it but I don't think my tablet is giving the correct info, or something??!?! When I run adb devices in CMD in the platform-tools directory it doesn't list any devices available. If anyone could help it'd be greatly appreciated. Could possibly upload a screenshot of my usb devices with the USBdeview software?
GermanDoerksen said:
Okay... so the other day in class I was thumbing through the intrawebs and noticed the leaked ICS had came out for the A500... I tried flashing the ROM to my tablet, thinking it would be a cinch if I just followed the directions. No go, just stuck on Android boot logo. That's fine and all, made a back up with CWM (which i think was my initial problem with the ICS version.. correct if I'm wrong please,) but... my back-ups check sums were mismatching for everything. Couldn't get them to match and couldn't figure it out so I decided to just flash root stock version back on to the tablet and go from there using my titanium backup.
I flashed, and bam... vibrating black screen, no CWM recovery anymore no matter what I do. I've been using the SDK manager / ADB terminal thinger / EUUS Acer Iconia Tab Software Upgrade Utility. I cannot for the life of me find my CPUID, or at least the RIGHT CPUID. I understand to use software to find it but I don't think my tablet is giving the correct info, or something??!?! When I run adb devices in CMD in the platform-tools directory it doesn't list any devices available. If anyone could help it'd be greatly appreciated. Could possibly upload a screenshot of my usb devices with the USBdeview software?
Click to expand...
Click to collapse
To get your old uid number, look in one of your cwm backup folders on your SD card.should say uid.txt.
Then you can either use the photo tutorial at androidtabletgeeks.com, or there is text instructions here at xda.
Also, sounds like you may need to load the a DB drivers for your tab.
Help ME!!!!!!!!!!!!!
I've got a similar problem. My A500 are with the Boot "Verified Boot failed" and no way I can make it work again. He was with the ICS ROM'm trying to make it back to the Stock ROM but I can not. Please Help Me.
Hmm...
Moscow Desire said:
To get your old uid number, look in one of your cwm backup folders on your SD card.should say uid.txt.
Then you can either use the photo tutorial at androidtabletgeeks.com, or there is text instructions here at xda.
Also, sounds like you may need to load the a DB drivers for your tab.
Click to expand...
Click to collapse
Okay, that got me started in a good direction I feel like. The only problem is that CWM made them all "*.img" files. There is a "system.img", "boot.img", and "recovery.img". Which one should I be trying to tear into to get it? And I'm pretty sure I have the adb drivers installed, or at least my device shows up in my device manager when I put it in APX mode, and I've downloaded the USB recovery drivers from the ACER website, along with other drivers that people have suggested.
Thanks for your quick reply! Hopefully this gets me somewhere, if you have any more suggestions on where to find it within the filesystem / *.img files let me know.
** Also a "data.img"... didn't want to leave the right one out on accident haha.**
Still nothing...
I've been trying to go through the old CWM back up .img files, but the only one I can even open and extract is the system.img which from what I can tell, has nothing to do with the CPUID. Next I started up a virtual ubuntu to try ADB out on there, same results. Even changed the vendor ID to the one given to me by lsusb, still nothing. I'm out of thoughts on this... I'm burnt out on trying to get this to work.
When I opened up usbdeview, I saw an old version of my Acer Iconia tab when it was actually working. Used that serial number and it made it through to where it said it was upgrading, but then sat/hung overnight. didn't move or make any progress so I unplugged it so I could go to class and keep working on it... now that cpuid doesn't work either.
Is my tablet a fancy paperweight now?
A500 Reborn
People,
I managed to make my A500 back to work with an update file, but forum cannot permit to put the link here. Take out the spaces of the link below:
www . fileserve . com / file / 2HUVP9D / update(ok) . zip
Rename the file to "update.zip", then save this on Sdcard and Boot the A500 with Vol - pressed.
Worked for me.
so..
assanches said:
People,
I managed to make my A500 back to work with an update file, but forum cannot permit to put the link here. Take out the spaces of the link below:
www . fileserve . com / file / 2HUVP9D / update(ok) . zip
Rename the file to "update.zip", then save this on Sdcard and Boot the A500 with Vol - pressed.
Worked for me.
Click to expand...
Click to collapse
Did you have a recovery that you were able to boot into when you did this? Or does holding vol - while powering up install the update.zip? If you used a recovery manager it's not going to help me at all.
A500 Reborn
GermanDoerksen said:
Did you have a recovery that you were able to boot into when you did this? Or does holding vol - while powering up install the update.zip? If you used a recovery manager it's not going to help me at all.
Click to expand...
Click to collapse
I did this without a CWM recovery, only stock recovery (holding vol - while powering up).
assanches said:
I did this without a CWM recovery, only stock recovery (holding vol - while powering up).
Click to expand...
Click to collapse
Yeah... thanks but nothing doin for me. I have nothing but a black screen that vibrates. adb mode and such but nothing else. Something's gotta give eventually.
A500 Reborn
GermanDoerksen said:
Yeah... thanks but nothing doin for me. I have nothing but a black screen that vibrates. adb mode and such but nothing else. Something's gotta give eventually.
Click to expand...
Click to collapse
GermanDoerksen,
Did you try this?
http://forum.xda-developers.com/showpost.php?p=18750804&postcount=17
Worked for many users.
yup
assanches said:
GermanDoerksen,
Did you try this?
http://forum.xda-developers.com/showpost.php?p=18750804&postcount=17
Worked for many users.
Click to expand...
Click to collapse
That's where I started this journey to get it working again lol. The only problem I'm having is with finding my CPUID or the UID he talks about. The numbers I get don't work because they're for the recovery driver, not an actual UID for my tablet. There is no serial number displayed when connected.
GermanDoerksen said:
That's where I started this journey to get it working again lol. The only problem I'm having is with finding my CPUID or the UID he talks about. The numbers I get don't work because they're for the recovery driver, not an actual UID for my tablet. There is no serial number displayed when connected.
Click to expand...
Click to collapse
have you tried using usbdeview to find the cpuid?
look at the beginning of my post here: http://forum.xda-developers.com/showpost.php?p=22902126&postcount=258
wolverine423 said:
have you tried using usbdeview to find the cpuid?
look at the beginning of my post here: http://forum.xda-developers.com/showpost.php?p=22902126&postcount=258
Click to expand...
Click to collapse
Well I had... but I think you just helped me out. Will these show up if I'm using the recovery driver to get it to be recognized? I can find it when plugged in under Acer Iconia, but I think that's from a previous plug-in before I flashed it. Now when I plug it in it comes up under "acer picasso recovery driver". I never new what vendor ID to look for, so I'm going to do that.
Do I have to put serial number in the .txt file named cpuid to get it to work?
Thanks for replying and giving me something to do!
wolverine423 said:
have you tried using usbdeview to find the cpuid?
look at the beginning of my post here: http://forum.xda-developers.com/showpost.php?p=22902126&postcount=258
Click to expand...
Click to collapse
Okay, so I'm in my college class so I don't have my own laptop with me, I'm trying this on a "frozen" desktop. I said earlier my tablet show up in usbdeview as acer picasso recovery driver, but it flip flops between that and acer USB-Boot recovery driver. Don't know why. Either way, when I plug my tablet into my computer and put it in APX mode, it shows up, but no serial number or anything. I'm going to try what you said on my laptop at home where I've plugged it in before I flashed it, maybe I can find it then. Hopefully. Here's a USBdeView picture of what I'm seeing when I plug my tablet in.
woops
Sorry, picture was blurry...
GermanDoerksen said:
Sorry, picture was blurry...
Click to expand...
Click to collapse
Our computer labs all use deepfreeze.
Yeah, it should be listed on your laptop if it was plugged in while running honeycomb.
Best of luck.
wolverine423 said:
Our computer labs all use deepfreeze.
Yeah, it should be listed on your laptop if it was plugged in while running honeycomb.
Best of luck.
Click to expand...
Click to collapse
Hey so do ours. Gotta love the key combination to get past it
But that's awesome, this gives me hope! Will try this if I ever get out of this class... yay for linux classes that last from 8 to 3.
I have also bricked mine due to not reading things before jumping in as usual doh.
I installed the lightspeed ics beta 5 and it was pretty nice but a game I have been playing kept freezing so I decided to go back to 3.2 official by putting it on the sd card and booting recovery. It went through install etc but then just goes to a bootloop with the blue lightspeed flashing adroid. CWM is no more and like an idiot did not get my cpuid prior.
I tried installing the 3.0.1 unstable too but that did not work either. It just sits on flashing android now.
Will I have to wait until an official acer ics update.zip is available once released?
Thanks in advance
waj1234 said:
I have also bricked mine due to not reading things before jumping in as usual doh.
I installed the lightspeed ics beta 5 and it was pretty nice but a game I have been playing kept freezing so I decided to go back to 3.2 official by putting it on the sd card and booting recovery. It went through install etc but then just goes to a bootloop with the blue lightspeed flashing adroid. CWM is no more and like an idiot did not get my cpuid prior.
I tried installing the 3.0.1 unstable too but that did not work either. It just sits on flashing android now.
Will I have to wait until an official acer ics update.zip is available once released?
Thanks in advance
Click to expand...
Click to collapse
I don't think you'd HAVE to wait for the office ICS update. For you, I'd say do what I've been trying to do which is get it back to stock rom and recovery manager so I can wait for the official ICS update. Eventually, if I ever do unbrick this thing, then I will have to decide if I want to wait or not. Or dual-boot ubuntu
GermanDoerksen said:
I don't think you'd HAVE to wait for the office ICS update. For you, I'd say do what I've been trying to do which is get it back to stock rom and recovery manager so I can wait for the official ICS update. Eventually, if I ever do unbrick this thing, then I will have to decide if I want to wait or not. Or dual-boot ubuntu
Click to expand...
Click to collapse
I cant get my cpuid though as it dont show in usbdview either unless I need the drivers from sdk first.
I made stupid mistake by updating my TPT to ICS by CWR, now I can not get in CWR and system anymore. What should I do?
How do I get my CWR back?
Can you still see the device in ADB shell? I'm not but I would search some of the ICS update threads in this section, I think someone else did what you did.
daswahnsinn said:
Can you still see the device in ADB shell? I'm not but I would search some of the ICS update threads in this section, I think someone else did what you did.
Click to expand...
Click to collapse
Thank you for your reply.
I will try to find the answer then.
PLZ Let me know if you got something
You should be able to access the recovery via adb, and push file to the system, but be careful read up on it before do it it will save you later.
yirsung said:
Thank you for your reply.
I will try to find the answer then.
PLZ Let me know if you got something
Click to expand...
Click to collapse
You maybe use APX/NVFlash Mode, It is a micro code than in NVIDIA Tegra CPU ROM,
1. connect use micro USB line to computer,
2. Press POWER and Screen rotation lock togther,
3. a new device "APX Device" is apper at Device management
4. Update APX Driver
5. Use nvflash command line write booloader(Lenovo, ClockWorkMod,etc)
you can find a thread at 51nb forum
i'm curious if this got resolved.
I'm in the same predicament and trying to use the apx nvflash utility without any luck
After losing recovery and root on my tpt, I spent hours trying to fix it with no success. I had no recovery, no adb shell, and no root access so I couldn't change anything. I couldn't use nvflash(locked bootloader--that was my last resort). Ended up sending it to Lenovo and it supposed to be in process of getting repaired now
Elite thanks in advance. No, seriously, thanks. I'm a broke single parent of 2 kids and I realized my phone is about my only guilty pleasure after giving my kids 200% of my time and money. Any help would be appreciated.
I have an LG G2 that I apparently bricked by using an app to "freeze" the latest OTA software update that was pushed to my ATT LG G2 about a month + ago if not slightly longer. I unfroze the process and the update suddenly appeared and said it would reboot the phone and or apply the update it in 30 seconds. I panicked and held the power button in to turn the phone off.
Once the phone was turned back on I was greeted with tiny white text that said "error: Boot certification verify" From here I was unable to get into down load mode, do a hard reset. I was able to see fast boot mode but wasn't sure what to do with it. I was able to see the phone in Windows 7 Pro Sp1 device manager but it was listed as QHSUSB_BULK
After initially freaking out which lasted about 20 mins, I was able to compose myself and start researching my new seemingly serious problem. After a few hours of reading a dozen or so treads / hundreds of replies it seemed I would have to load into Ubuntu and push some files to my LG G2.
I followed this guide - http://forum.xda-developers.com/showthread.php?t=2582142
I was very careful to follow this guide to the letter and everything went as expected the first, 2nd and 3rd time only the results were worse and worse and worse.
The first time I lost fast boot, the 2nd time I lost the boot certification verify error, After the 3rd attempt I get a split second LG Logo and that's it. What did I do during those 3 attempts? The first time, the 4 files and the recovery as directed. The 2nd time, the same files, plus the boot.img and a different recovery. The 3rd time, all the files and yet a different recovery. All the files were pulled from here - http://downloads.codefi.re/autoprime/LG/LG_G2/D800
The other recovery.imgs were for the correct model, just older, newer variants. I was very careful to push the right files to the right partitions.
I can still see the phone via Ubuntu. I'm scared to do anything else along the lines of what I've been doing. In fact I'm lost as to what to do next.
Can anyone here help me push more / different files via Ubuntu that would help bring my phone back to life? I'm completely dead in the water. Or perhaps an exe package / program that can fix my problem? If I sound stupid, it's because this is all new to me.
Thanks in advance, Tom
@rthefley Go back to the autoprime downloads and get the boot, aboot and laf image. Follow the ubuntu guide and flash those images only.
@art
Thank you for taking the time to stop and help me. I greatly appreciate it. I followed your instructions and pushed those 3 files in the order you gave me. Results were the same, nothing. I still get a very brief LG logo but nothing more. I can get into the hard reset but it does nothing as well.
Here are pics I took of the files and directories from my phone connected via usb through Ubuntu. There are a few wrong commands, ignore them. GF was behind me talking and I wasn't focused. I can assure you the proper cmds were given when it counted.
Well ....... I guess I cannot post links ............. so they are edited out. I wanted to show that my highest number was sbe43 so I had to use sbe
Im using the files from the D800 dir which is the ATT LG G2. Or should I tried another directory or files? I can still access the phone via Ubuntu ... THANK GOD
I am still hopeful.
rthefley said:
@art
Thank you for taking the time to stop and help me. I greatly appreciate it. I followed your instructions and pushed those 3 files in the order you gave me. Results were the same, nothing. I still get a very brief LG logo but nothing more. I can get into the hard reset but it does nothing as well.
Here are pics I took of the files and directories from my phone connected via usb through Ubuntu. There are a few wrong commands, ignore them. GF was behind me talking and I wasn't focused. I can assure you the proper cmds were given when it counted.
Well ....... I guess I cannot post links ............. so they are edited out. I wanted to show that my highest number was sbe43 so I had to use sbe
Im using the files from the D800 dir which is the ATT LG G2. Or should I tried another directory or files? I can still access the phone via Ubuntu ... THANK GOD
I am still hopeful.
Click to expand...
Click to collapse
In that case, you should try to push a recovery image, too!
Raymonf said:
In that case, you should try to push a recovery image, too!
Click to expand...
Click to collapse
I've pushed 4 or 5 different recovery images. Should I try something different than the recovery images suggested? I am willing to try anything at this point.
rthefley said:
I've pushed 4 or 5 different recovery images. Should I try something different than the recovery images suggested? I am willing to try anything at this point.
Click to expand...
Click to collapse
Did you lokify them?
Raymonf said:
Did you lokify them?
Click to expand...
Click to collapse
@Raymonf first let me thank you for taking the time to try and help me sort out my ... what I consider a serious issue. Thank you!
I've not read about lokify. So I am not sure what that is but I can absolutely tell you, I'm a great listener. I've spent 12 or 13 hours reading all over the internet, tread after tread and post after post. So I somehow missed the instructions on lokifying the files.
Tom
rthefley said:
@Raymonf first let me thank you for taking the time to try and help me sort out my ... what I consider a serious issue. Thank you!
I've not read about lokify. So I am not sure what that is but I can absolutely tell you, I'm a great listener. I've spent 12 or 13 hours reading all over the internet, tread after tread and post after post. So I somehow missed the instructions on lokifying the files.
Tom
Click to expand...
Click to collapse
Okay, are you now able to go into download mode?
1127
Art Vanderlay said:
Okay, are you now able to go into download mode?
Click to expand...
Click to collapse
No, I've never been able to get into the download mode.
The only way I can access my phone is via Ubuntu. Hard Reset doest work even though I can get to that screen and initiate the process, it doesn't complete.
One other person that's also trying to help me out asked if I've lokify those img files. No I haven't. I've not come across those instructions yet. Would that make a difference?
I also sent you a private PM with links to pics I took of my directory structure from my ATT LG G2 via usb / Ubuntu
rthefley said:
No, I've never been able to get into the download mode.
The only way I can access my phone is via Ubuntu. Hard Reset doest work even though I can get to that screen and initiate the process, it doesn't complete.
One other person that's also trying to help me out asked if I've lokify those img files. No I haven't. I've not come across those instructions yet. Would that make a difference?
I also sent you a private PM with links to pics I took of my directory structure from my ATT LG G2 via usb / Ubuntu
Click to expand...
Click to collapse
Your directories are fine. But if you successfully flashed those 3 partitions, you should Have a working download mode. Make sure you fully power off the phone, you might have to hold the button down for a while.
Art Vanderlay said:
Your directories are fine. But if you successfully flashed those 3 partitions, you should Have a working download mode. Make sure you fully power off the phone, you might have to hold the button down for a while.
Click to expand...
Click to collapse
Yes I'm pretty sure it's completely powered off. I will try again but I've held the power button in for several several seconds and saw the screen go solid black. I've flashed those 3 files just as instructed. Nothing is working sadly. Maybe I am missing some key procedure others take for granted that I just personally do not know about
Is there anything else I could try doing? I'm going in circles here.
Do your results match the one in the forum when you type gdisk -l /dev/sdb in the terminal.? Also is your fastboot still gone.?
Sent from my LG-LS980 using Tapatalk
LilDemon124 said:
Do your results match the one in the forum when you type gdisk -l /dev/sdb in the terminal.? Also is your fastboot still gone.?
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
No they are different, I actually gdisked all of the different letters but I have an sda,c,b and e, I even have have an sde1. All the numbers follow sde however up to 42 or 43. So when I gdisk -l /dev/sde that's when I see all the files.
I've tried to gdisk sdb but I get a mbr / gpt or something error saying something is corrupted so I just leave it alone.
Should I be looking at a different letter then? If so, I can't seem to get into any of them other than the one I mentioned, sde
Guys, I'm now offering a $40 paypal bounty directly to your pocket or a donation to this web site for help allowing me to get back into my phone.
I will try my best to help you. Im at work, but will be home soon so that I can do some snooping.. From what your saying you MIGHT have a corrupt storage OR you might have a corrupt file.
Sent from my LG-LS980 using Tapatalk
Im going to have to work on this a bit later. Worked all day. I'm still here and around just need to get a little sleep before I even think of trying to dive into this again. Thanks.