Related
I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.
lbloo said:
I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.
Click to expand...
Click to collapse
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.
I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?
lbloo said:
I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?
Click to expand...
Click to collapse
rooted stock ROM yea. I've also flashed a pure aosp ROM over stock without any reprocussions.
Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.
lbloo said:
Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.
Click to expand...
Click to collapse
I don't know what you picked up, but here's a stock/rooted ROM that you can flash in your cwm recovery http://forum.xda-developers.com/showthread.php?t=1776330
Aosp works too, its your choice
if you know how to use adb you can just boot to recovery and push the stock build.prop to your tab
I downloaded a stock copy of the stock build.prop, used the adb push command to push it into /system rebooted and nothing. Still hangs on black screen upon boot.
I then downloaded the stock ROM which simms22 kindly pointed me to, used the adb push command to copy the zip file into /data/media/Firmware, used CWM v6.0.1.0 to "install zip file from sdcard" and I got an error, here is the output:
Installing:/sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
Finding update package...
Opening update package...
Installing update package...
E:Error in /sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
(Status 0)
Installation aborted.
I tried both the Odexed and Deodexed files, both gave same results.
Am I missing a step in the process?
It's working now!
I was afraid I was messing up some of the adb commands so I downloaded the Nexus 7 Toolkit 2.0 (Great tool for someone like me)
- via Toolkit re-transferred the odexed and deodexed ROM files, reflashed, same errors as above
- via Toolkit re-installed CWM Recovery 6.0.1.0, reflashed, same errors as above
- via ADB Shell used CHMOD to modify file rights of the ROM files (stab in the dark), same errors as above
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Not sure why the other ROMS would not flash, but at this point I'm not going to mess around to try to figure it out.
Many thanks to simms22 and PhxkinMassacre for getting me pointed in the right direction.
prly a bad download.
after pushing the file you need to set the correct mode:
Code:
adb shell chmod 644 /system/build.prop
Me too - also hosed my own build.prop
lbloo said:
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Click to expand...
Click to collapse
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack
Looking back I don't recall resetting the file rights after modifying the file and that was likely the root cause of my problems.
You should try the chmod command a couple of posts back.
JackinNC said:
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack
Click to expand...
Click to collapse
What location did you push it to? /sdcard/?
Sent from my Nexus 7 using xda app-developers app
mvmacd said:
What location did you push it to? /sdcard/?
Click to expand...
Click to collapse
Yes. And, to further test, I created a little zip file called test.zip and pushed it to the tablet. I can see it just fine. It's just the grouper zip that I can't find.
Thanks
Jack
I just noticed a diff in filesize between the JRO03D_grouper.zip file I am using and one shown in a Youtube video entitled "how to put a rom to flash on a semi-bricked nexus 7 with recovery" by Youtube user metroid031993. (I'm too green to post outside links on XDA)
Mine is 261814702 bytes, the one shown in the video is 32650144 bytes.
Perhaps this is my problem, an invalid zip file. What do you think? And, can someone please tell me the correct size of JRO03D_grouper.zip?
Thanks
Jack
[Note to moderator(s): If I am heading off track in this thread, please don't hesitate to move it or to instruct me to create a new thread. I think the issue may have changed, but I have stayed here since this is where the conversation is for my root issue. Thx!]
JackinNC said:
can someone please tell me the correct size of JRO03D_grouper.zip?
Click to expand...
Click to collapse
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.
Visa Declined said:
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.
Click to expand...
Click to collapse
Thanks for the confirmation.
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
---------- Post added at 11:19 AM ---------- Previous post was at 10:51 AM ----------
JackinNC said:
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
Click to expand...
Click to collapse
Well, I got the grouper zip into /sdcard/ and was able to upgrade without losing anything. w00t!
Theory:
I was in the same adb "session" this time since I was using adb from the command line. Meaning, the daemon was still running from the first push I did. So, while I couldn't see the grouper zip after the first push (consistent with your experience, dark_samus), I could see it and upgrade with it after second push (also consistent). And, perhaps my previous attempts didn't work before because I was closing and opening the Nexus 7 Toolkit each time, therefore stopping and restarting the daemon, which meant that each push attempt was the first attempt for that "session."
I don't have any solid technical basis to support or refute that theory, it's just one possible theory that, if true, would result in the experience I had.
My problem is resolved. Thanks to everyone who contributed to this, I truly appreciate your help!
Jack
simms22 said:
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.
Click to expand...
Click to collapse
how to put the stock image if my n7 doesnt boot to android? pls help
i have CWM already
Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
my bad i already flash a fresh stock rom again, but thanks anyways...
i downloaded a custom rom and gapps to flash to my nexus, went to recovery to flash, wiped everything including system, when i go to flash the custom rom, BAM !!!!! it didnt download only the gapps did. now i have NO OS , no nandroid backup and no Custom Rom to flash
Pretty stupid of me not to have a nandroid backup but with the storage limitations of 8GB, i didnt do one to save space for other stuff, So basically i have an unlocked bootloader and custom recovery installed, can someone point me in the right direction on how to install an OS to my phone again
You could download ROM to your computer and use adb push to copy it to the phone where you can flash it,
Sent from my GT-P3110 using Tapatalk 2
CptanPanic said:
You could download ROM to your computer and use adb push to copy it to the phone where you can flash it,
Sent from my GT-P3110 using Tapatalk 2
Click to expand...
Click to collapse
I see an option on TeamWin recovery called ADB Sdeload, but i have no idea how to use it.
edit.. see below for command
just download a complete rom and name it rom.zip and put it where you have your adb.exe and fastboot.exe files, make sure to run the command from where you have the files, then just go into recovery and flash it
AW: [q] wiped android system, no nan backup
Go in with "ADB push c:\rom.zip /SDCARD/" this will copy your ROM from your PC to your Nexus. Then you can flash it via your recovery.
In general you can look if a ADB connection is working properly with typing "adb devices". After this you can push your file to your phone.
Gesendet von meinem Nexus 4 mit Tapatalk 2
Could you possibly push it with the nexus4 tool kit it has a flash stock option? Just my two cents just got the phone so I could be wrong
Sent from my Nexus 4 using xda premium
http://forum.xda-developers.com/showthread.php?t=1995688
Install the Nexus 4 Toolkit from the link above... It will install on your C: drive... C:/Google Nexus 4 Toolkit...
Follow the instructions and download the adb files for 4.2.2 found on this page...
Extract them to the folder above, writing over the ones that already exist.
Next, go to https://developers.google.com/android/nexus/images#occam and download the factory rom for 4.2.2
Paste the rom in C:/Google Nexus 4 Toolkit/put_google_factory_image_here
Next, open the .exe called Toolkit in this folder.
Check for update? Say no.
What build do you have? 1
You are now at the main menu...
Select the number 9
Now put your phone in Fastboot mode..
Once its in fastboot mode, type yes and press enter... it will now flash to stock.
This version of the toolkit will not root, b/c adb is different or something... But it will still flash touch recovery, using option 6.
From there you can do what you want, flash a new rom or root stock.... Have a nice day! And click the Thanks button please,
I'm not on often enough to get Thanks....
P.S. I did the same thing yesterday... I'm so used to just wiping everything on my stupid skyrocket.... lol.
But I wanted to do a fresh install b/c I was having some issues with my titanium backup files from the lates rom i was
using on my skyrocket... so now i'm going old school, reinstalling everything one by one from the market... Then i'll do another
titanium backup and a full backup to have a restore point... Makes for a fun weekend...
jpierce1987 said:
http://forum.xda-developers.com/showthread.php?t=1995688
Install the Nexus 4 Toolkit from the link above... It will install on your C: drive... C:/Google Nexus 4 Toolkit...
Follow the instructions and download the adb files for 4.2.2 found on this page...
Extract them to the folder above, writing over the ones that already exist.
Next, go to https://developers.google.com/android/nexus/images#occam and download the factory rom for 4.2.2
Paste the rom in C:/Google Nexus 4 Toolkit/put_google_factory_image_here
Next, open the .exe called Toolkit in this folder.
Check for update? Say no.
What build do you have? 1
You are now at the main menu...
Select the number 9
Now put your phone in Fastboot mode..
Once its in fastboot mode, type yes and press enter... it will now flash to stock.
This version of the toolkit will not root, b/c adb is different or something... But it will still flash touch recovery, using option 6.
From there you can do what you want, flash a new rom or root stock.... Have a nice day! And click the Thanks button please,
I'm not on often enough to get Thanks....
P.S. I did the same thing yesterday... I'm so used to just wiping everything on my stupid skyrocket.... lol.
But I wanted to do a fresh install b/c I was having some issues with my titanium backup files from the lates rom i was
using on my skyrocket... so now i'm going old school, reinstalling everything one by one from the market... Then i'll do another
titanium backup and a full backup to have a restore point... Makes for a fun weekend...
Click to expand...
Click to collapse
Bro you're a lifesaver, i wish i could hit the thanks button 20 times lol. Thanks a lot
Hey all...I'm sorry for sounding like such a noob (trust me i'm not as big as one as you may think) I'm just having a hard time grasping the idea of updating my Nexus. Let me explain:
I'm currently running stock rom but have Matr1x kernel on my phone. The only thing I've changed so far are a few icons (by pulling files from the nexus toolkit, replacing the icons and pushing them back to my phone).
I would prefer not to have to go through and redo all my icons, and would just like to get 4.2 onto my phone.
I looked over the directions on how to do this, but for the life of me (and IDK why) i can't seem to get my head around it...and it's making me feel real real stupid...
can someone please explain to me like i'm 5 how to do this? Or maybe just point me in the direction of a youtube video that will walk me through it...?
Thanks in advance and sorry for being such a noob...
Why not just backup the apk's+data you edited, save them to your computer, flash the stock images, root and restore the apps+data?
Edit: And flash a 4.2.2 kernel.
estallings15 said:
Why not just backup the apk's+data you edited, save them to your computer, flash the stock images, root and restore the apps+data?
Edit: And flash a 4.2.2 kernel.
Click to expand...
Click to collapse
Do I backup via toolkit or with titanium backup?
Also, i tried getting back to stock but for some reason couldn't get it to flash the img file...idk what i was doing wrong...maybe u can give me some pointers on it.
Idk y i'm having such trouble with this, i've been on android since the very begining (had a g1 2 months after it came out)...I guess I was just spoiled with my vibrant being so easy...
zbt1985 said:
Do I backup via toolkit or with titanium backup?
Also, i tried getting back to stock but for some reason couldn't get it to flash the img file...idk what i was doing wrong...maybe u can give me some pointers on it.
Idk y i'm having such trouble with this, i've been on android since the very begining (had a g1 2 months after it came out)...I guess I was just spoiled with my vibrant being so easy...
Click to expand...
Click to collapse
First of all, ditch the toolkit. You don't learn anything when you use toolkits. Probably why you're in the situation you're in.
Backup with titanium, or just make a nandroid and use titanium to extract the apps later.
To flash stock images:
Reboot into bootloader.
Open command prompt and "cd" to the directory where fastboot lies.
Type these commands -
fastboot flash system system.img
fastboot flash boot boot.img
Optional -
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Then reboot
estallings15 said:
First of all, ditch the toolkit. You don't learn anything when you use toolkits. Probably why you're in the situation you're in.
Backup with titanium, or just make a nandroid and use titanium to extract the apps later.
To flash stock images:
Reboot into bootloader.
Open command prompt and "cd" to the directory where fastboot lies.
Type these commands -
fastboot flash system system.img
fastboot flash boot boot.img
Optional -
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Then reboot
Click to expand...
Click to collapse
Here's where the confusion lies...what do u mean cd where fastboot lies...I know how to cd, but not sure what you mean by where the fastboot would be...
zbt1985 said:
Here's where the confusion lies...what do u mean cd where fastboot lies...I know how to cd, but not sure what you mean by where the fastboot would be...
Click to expand...
Click to collapse
I extract the adb folder from the android SDK and drop it in C:\.
So for me, it's "cd C:\adb"
I believe in the SDK it's in platform-tools or some such jazz. You can always do a search on your computer...
You have installed the android SDK, right? If not, your toolkit might have the adb and fastboot files in it. Grab them from there. Make it work. You can do it.
estallings15 said:
I extract the adb folder from the android SDK and drop it in C:\.
So for me, it's "cd C:\adb"
I believe in the SDK it's in platform-tools or some such jazz. You can always do a search on your computer...
You have installed the android SDK, right? If not, your toolkit might have the adb and fastboot files in it. Grab them from there. Make it work. You can do it.
Click to expand...
Click to collapse
Yes I have the SDK as I use eclipse to complie the apps i make (i cheat)...
I see adb.exe, but not the folder for adbe...
Thanks for all the help man, I hit the thanks button for u!
zbt1985 said:
Yes I have the SDK as I use eclipse to complie the apps i make (i cheat)...
I see adb.exe, but not the folder for adbe...
Thanks for all the help man, I hit the thanks button for u!
Click to expand...
Click to collapse
There should be a fastboot.exe and a few .dll files, as I recall.
Could someone upload all the latest files needed for adb and fastboot in a zip for him? Won't take you 5 minutes. I'm not by my computer.
Why not flash CM10.1 or latest Xylon.
Back up apps with titanium, flash ROM, flash gapps, restore via titanium.
Or do you want stock?
[Nexus⁴]
dEris said:
Why not flash CM10.1 or latest Xylon.
Back up apps with titanium, flash ROM, flash gapps, restore via titanium.
Or do you want stock?
[Nexus⁴]
Click to expand...
Click to collapse
I wanted stock...i only want this for 1) getting updates faster than cm 2) being able to update the hard way and not be a kiddy about it...
Better for me to learn...
http://forum.xda-developers.com/showthread.php?t=2145848
Scenario #3
Continue to section C.
Sent from my Nexus 4 using xda premium
just follow efran's guide, he got the step by step: http://forum.xda-developers.com/showthread.php?t=2010312
gravitysandwich said:
http://forum.xda-developers.com/showthread.php?t=2145848
Scenario #3
Continue to section C.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
That's what is confusing me...
Sent from my Nexus 4 using xda app-developers app
Download this http://d-h.st/iy0. Unzip it. Plug your phone I'm the computer, go to the directory where you installed the toolkit. (Right click on the shortcut/properties it should say it there) go in the directory, FLASH ITEMS HERE folder. Put the boot.img and system.img in there. (Radio.img is optional). Open the toolkit and go to flash images. Flash boot.img first. The directions should be on the toolkit. Then system and etc... Make sure you put it in fast boot or type no when the toolkit asks if your in fastboot mode. This will NOT delete your data. When you flashed everything, go to settings on your phone. (If there is a bug with updating it through settings, clear cache and data for Google services framework and force stop it. Then go to cache on root explorer (/cache) and delete the corrupt/partial update and try Again). Once you reboot, cwm will ask if you want to install update. Hit yes and install untrusted package. Then it will try to replace cwm with stock recovery so hit no. If you lost your root then get supersu from the play store and install the binaries via cwm.
Hope this helps.
Sent from my Nexus 4 using xda premium
---------- Post added at 12:11 AM ---------- Previous post was at 12:02 AM ----------
Btw I chose to flash it through toolkit because I was afraid you would've got the commands mixed up and you would never get it. One day you probably will
Sent from my Nexus 4 using xda premium
Muchos gracias.
Would thank but on my phone
Sent from my Nexus 4 using xda app-developers app
zbt1985 said:
Muchos gracias.
Would thank but on my phone
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You can thank you your phone.
So it worked? Your welcome. I'm guessing you lost root. Here is the zip if you need it
http://download.chainfire.eu/314/SuperSU/UPDATE-SuperSU-v1.20.zip
Sent from my Nexus 4 using xda premium
gravitysandwich said:
So it worked? Your welcome. I'm guessing you lost root. Here is the zip if you need it
http://download.chainfire.eu/314/SuperSU/UPDATE-SuperSU-v1.20.zip
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Haven't had a chance to try it, doing it now...thanks!
I flashed TWRP to make backups and am finding I want to revert to stock recovery for whenever the next OTA is pushed. I'm on stock 4.2.2. Is there a repository to flash the stock recovery specific to the version of android I'm on or other way to backup/re-flash stock android prior to installing custom recovery?
ravenofdoom said:
I flashed TWRP to make backups and am finding I want to revert to stock recovery for whenever the next OTA is pushed. I'm on stock 4.2.2. Is there a repository to flash the stock recovery specific to the version of android I'm on or other way to backup/re-flash stock android prior to installing custom recovery?
Click to expand...
Click to collapse
The stock Android recovery cannot make entire system (NANDROID) backups like TWRP or CWMR can. If your looking to re-install stock Android 4.2.2 for the Nexus 10 you can download and flash the Nexus 10 factory image from here (I would recommend taking a look at this great guide if your are unfamiliar with how to flash factory images). If you just want to reflash the Nexus 10 stock recovery you can download it from here, boot into fastboot mode and then flash it with the following command:
Code:
fastboot flash recovery path/to/recovery-stock-manta.img
After it completes you can reboot into recovery mode and you should now have the stock Nexus 10 recovery image installed. For flashing the stock recovery you should try and match it to the Android version so if your on Android 4.2.2 try and flash the recovery.img that was pulled from the Android 4.2.2 factory image. However usually you can get away with flashing 4.2 or 4.2.1 version of the stock recovery.img as it is unlikely that anything major changed with the stock recovery image in those small incremental Android updates.
Is there a repo or other way to make a backup of stock recovery before flashing custom (TWRP/CWMR). If I'm on the go and want to interchange between custom recovery and previous stock recovery without the aid of a computer nearby, how would I do that? Is there an app that can save/snapshot my current stock recovery before flashing custom recovery (and then can later let me re-flash that saved recovery)?
Flashing stock recovery wont make me lose any data will it? because 4.3 was released for s4 google edition so im sure nexus 10 is close and i want to be ready.
abdel12345 said:
Flashing stock recovery wont make me lose any data will it? because 4.3 was released for s4 google edition so im sure nexus 10 is close and i want to be ready.
Click to expand...
Click to collapse
Correct flashing stock recovery won't make you loose any data. But as always when your flashing anything and if you have even the slightest hesitation backup any data you wouldn't want to loose.
Sent from my SCH-I535 using xda premium
Alright thanks man. I already used my 8 for today but ill thank you tomorrow and ill back up my apps with titanium backup
OK what is the command to use to flash because the one from the previous page didn't work it said something about not finding it or something are there any drivers that need to be installed or something I'm missing? I connected it to my CPU and turned it on while holding power and volume and it went menu where you see tablet info? Any help please
Sent from my Xperia Play (r800x)
ravenofdoom said:
Is there a repo or other way to make a backup of stock recovery before flashing custom (TWRP/CWMR). If I'm on the go and want to interchange between custom recovery and previous stock recovery without the aid of a computer nearby, how would I do that? Is there an app that can save/snapshot my current stock recovery before flashing custom recovery (and then can later let me re-flash that saved recovery)?
Click to expand...
Click to collapse
Don't know if you still need this info, but you can use flash_image to flash recoveries without having to connect to a PC. So if you save the recovery image files, you can switch easily. Have a look here:
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
I haven't done this on my N10, but I've used the method several times on my HTC Vivid phone.
Sent from my Nexus 10 using Tapatalk HD
bruce7373 said:
Don't know if you still need this info, but you can use flash_image to flash recoveries without having to connect to a PC. So if you save the recovery image files, you can switch easily. Have a look here:
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
I haven't done this on my N10, but I've used the method several times on my HTC Vivid phone.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
That actually helped me out with my problem thanks because I couldn't get it to flash from cpu
Sent from my Xperia Play (r800x)
abdel12345 said:
That actually helped me out with my problem thanks because I couldn't get it to flash from cpu
Sent from my Xperia Play (r800x)
Click to expand...
Click to collapse
Cool. :thumbup:
Sent from my Nexus 10 using Tapatalk HD
@bruce7373 it didnt work it just tells me flash_image not found when i put in the command and i checked and its there on the sd card
abdel12345 said:
@bruce7373 it didnt work it just tells me flash_image not found when i put in the command and i checked and its there on the sd card
Click to expand...
Click to collapse
The IMG file is not found or flash_image itself isn't there? If you don't have flash_image, you can download it (I think there's a link on that page I referenced, or just Google it). If the former, you need to first navigate to the folder flash_image is in (/system/bin with the ROM I have on my N10), then run the command, making sure the IMG file is in the root of /sdcard.
Sent from my Nexus 10 using Tapatalk HD
bruce7373 said:
The IMG file is not found or flash_image itself isn't there? If you don't have flash_image, you can download it (I think there's a link on that page I referenced, or just Google it). If the former, you need to first navigate to the folder flash_image is in (/system/bin with the ROM I have on my N10), then run the command, making sure the IMG file is in the root of /sdcard.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
OK I'll try yhat
Sent from my Xperia Play (r800x)
So I am trying to install CM11 on my G2 D802. Root done, Loki done, CWM or TWRP recovery done, CM11 image and GApps on sdcard partition. Now there is just one problem. I need to transfer the boot.img file from the CM11 zip file, however, I am unable to enter the main booloader screen, thus the Fastboot option. When I try to do so, the phone just reboots normally and launches the Android. I have the same problem with both CWM and TWRP. Anyone have an idea as to what is wrong?
Not really sure what you are talking about. If you have recovery all you need to do is wipe system, data, and cache. Then install the CM11 zip.
Sent from my LG-VS980 using xda app-developers app
**** Ripple said:
Not really sure what you are talking about. If you have recovery all you need to do is wipe system, data, and cache. Then install the CM11 zip.
Sent from my LG-VS980 using xda app-developers app
Click to expand...
Click to collapse
I should start by mentioning, that the whole; Power and volume down button to enter bootloader never worked on the D802.
Basically what I need to do, is to transfer the boot.img file before flashing the .zip file, otherwise I will get bootloop (this is my second D802). That has always been the case for any Android device I have had.
So in order to flash the boot.img file, I must enter the Fastboot menu on my G2 before I can transfers the file via command prompt.
Stop what your doing read up before you try to do anything.
Sent from my LG-LS980 using xda premium
I've been flashing roms for years and nothing you are saying makes any sense. If you are having trouble entering recovery download terminal emulator. Open app and type su then press enter. You will be asked to grant root access assuming you have root. Then type reboot recovery, after that your phone will boot into recovery. Wipe, flash rom and gapps.
Sent from my LG-VS980 using xda app-developers app
shopperen said:
I should start by mentioning, that the whole; Power and volume down button to enter bootloader never worked on the D802.
Basically what I need to do, is to transfer the boot.img file before flashing the .zip file, otherwise I will get bootloop (this is my second D802). That has always been the case for any Android device I have had.
So in order to flash the boot.img file, I must enter the Fastboot menu on my G2 before I can transfers the file via command prompt.
Click to expand...
Click to collapse
If you downloaded CM11 for your device specifically then you do not need to flash a separate kernel (boot.img) it would be included in the ROM zip file.. As should be the case with any current ROM that is compatible with your model G2. If you were going to experiment by way of flashing some other G2 variant (ie. D800/1/3) which is not advisable btw on your D802 then I could see you flashing a kernel separately.
That said I agree with the person above me.. You should do a bit more reading so you understand these elements properly before ending up with a paper weight (or another one from the sounds of your post). Hope it helps good luck
Sent from my d800 using Tapatalk
th3g1z said:
If you downloaded CM11 for your device specifically then you do not need to flash a separate kernel (boot.img) it would be included in the ROM zip file.. As should be the case with any current ROM that is compatible with your model G2. If you were going to experiment by way of flashing some other G2 variant (ie. D800/1/3) which is not advisable btw on your D802 then I could see you flashing a kernel separately.
That said I agree with the person above me.. You should do a bit more reading so you understand these elements properly before ending up with a paper weight (or another one from the sounds of your post). Hope it helps good luck
Sent from my d800 using Tapatalk
Click to expand...
Click to collapse
Kernel files very depending on region. The distributor for LG phones in my country have altered the kernel in such a way, that the boot.img is required to be flashed.