[REQ] "Reboot" and "Recovery" in power menu - LG Optimus Black

Searching for a way to add "Reboot" and "Recovery" entries in power menu, I found this:
http://forum.xda-developers.com/showthread.php?t=811532
It seems to be pretty easy, but since I don't know how to do all that decompiling-modifying-recompiling of .apk and .jar files and how to adapt to our optimus black, I post this here. Maybe someone can do the job and share it to all of us as a flashable zip.
Cheers!

rgabi88 said:
Searching for a way to add "Reboot" and "Recovery" entries in power menu, I found this:
http://forum.xda-developers.com/showthread.php?t=811532
It seems to be pretty easy, but since I don't know how to do all that decompiling-modifying-recompiling of .apk and .jar files and how to adapt to our optimus black, I post this here. Maybe someone can do the job and share it to all of us as a flashable zip.
Cheers!
Click to expand...
Click to collapse
I think Noejn tried and couldn't yet. I had to try it, but until Wednesday I don't think I can...
But it would be great. Let's see if anyone can do it!
Enviado desde mi LG-P970 usando Tapatalk

i've tried it but i failed
it stuck bootlogo
we'd better to deodex framework files,but i can't,after i deodex,a "ERROR LG SECURITY TEAM" shows when bootup..
i deodex and mod it,and then i use dexopt-wrapper to get odex,and replace,failed
any idea?

I didn't follow that tutorial when I tried.
Unfortunately it didn't work. I can't seem to edit .jar files and boot the phone.
When I have more time I'll try an alternative to APKTool. Theming hates me.

Error lg security team
dxdiag32 said:
i've tried it but i failed
it stuck bootlogo
we'd better to deodex framework files,but i can't,after i deodex,a "ERROR LG SECURITY TEAM" shows when bootup..
i deodex and mod it,and then i use dexopt-wrapper to get odex,and replace,failed
any idea?
Click to expand...
Click to collapse
To solve this issue:
1-Download LG Mobile Support Tool to PC from lg.com/uk/support/mc-support/mobile-phone-support.jsp
2-Install USB drivers
3-Take the battery out then put it back. Press and hold Vol+ and connect the Phone to the PC using the USB cable while the LG Tool is running
4-From LG Tool select Customer support --> Recovery Phone then enter IMEI and select check
Wait until the download and then the flashing completes and you are done

Related

HONEYCOMBE-- 07-July-2011-- With GPS fix

If you like that I'm doing this, then a thanks is cool, PLEASE DONATE, TIME OR MONEY BUT GIVE SOMETHING TO THESE DEVS!
http://tabletroms.com/forums/showthread.php?356-Honeycomb-on-the-Adam-(Updated)
New - No more partition editing required!
HC16JUN2011
HD Video
-Changelog
Like with any rom, YOU MUST WIPE CACHE, SYSTEM AND DATA, this rom especially, the is a pre alpha and has issues with cache, if you don't clear your info every time you will run into problems. I also clear Dalvik Cache and Battery Stats.
Old info on how to partition
STEP 1 – You need the new NVFlash click here for the unpartitioned onces(may need these)
NVflash edit- pretty simple you need to change the android fastboot full, you'll find that file towards the top of the nvflash folder or you can download my premade ones: (BUT I DIDN'T FORCE YOU TO DOWNLOAD THESE, IF YOU BRICK YOUR DEVICE BY USING THESE THEN YOU BRICKED IT NOT ME, YOU HAVE BEEN WARNED)
Sorry about the mega upload, working on getting my server up, also CWM is untested, it had some problems but I believe that was due to file size.
Clockwork Mod folder
Stock Recovery Folder
The section your looking for looks like this
[partition]
name=APP
id=9
type=data
allocation_policy=sequential
filesystem_type=yaffs2
size=209715200 <---(here is the money)
file_system_attribute=0
partition_attribute=0
allocation_attribute=0x10
percent_reserved=0
filename=system.img
minus the arrow and the here is the money you'll find the size listed as 209715200, you need to change that to 536870912, once you save go to here to setup your APX drivers and prepare to flash according to the link
STEP 1.1 – THIS IS FOR CLOCKWORK MOD RECOVERY ONLY Download Here
Make a copy of your nvflash folder, I name it PIXEL QI CW Mod
STEP 1.2 – THIS IS FOR CLOCKWORK MOD RECOVERY ONLY
Thank you darknao
Quick & Dirty method :
Extract the recovery.img from the clockwork.zip, and copy it to the nvflash folder(replace the original one).
Step 2
You need then to put your device into force recovery mode, so turn off your device, then power it on while holding the power + the volume down button till a orange and a yellow lite light up.
Step 3
Run the download.bat file described in the nvflash or unbrick your adam thread - now you can change the file name of the rom to update.zip and flash freely!
Reserved for other usage
Any idea when we'll get gapps working? Or you just linking to what they have done? Thanks for working to spread the word.
Amon Darthir said:
Any idea when we'll get gapps working? Or you just linking to what they have done? Thanks for working to spread the word.
Click to expand...
Click to collapse
Gapps are included however this build didn't have them, they had alot of problems with the sync feature, but in theory you should be able to use the latest gingerbread gapps, I will test that right now.
-OK I tested it out, the google setup frooze up on me, after restarting I was able to get into the initial setup, but I have the wifi only model, so I'm going to look into the gapp issue, see if I can find a way around.
-Tried a couple more copies of gapps including a HC edit for the nook sdk HC-- I would press more into this but with the rate of the updates I think its kinda pointless, for now Im going to adb push the market and see what I can get working, hopefully not in-vain since MrGuy and DJSteve move so fast with the updates.
after you use nvflash it will start to boot.. (this would be before flashing update zip) so should I power it down while its booting that first time in order to reboot to recovery and flash the zip?
I do but you don't have to if you use clockwork mod, it doesn't really matter, since you will be building your Dalvik cache once you install your rom.
$ ./download.sh
./nvflash: ./nvflash: cannot execute binary file
can anyone help me with this error i am getting when trying to run the downlaod script
jakobdroid said:
$ ./download.sh
./nvflash: ./nvflash: cannot execute binary file
can anyone help me with this error i am getting when trying to run the downlaod script
Click to expand...
Click to collapse
what operating system do you have? Is your adam in apx mode, and did you edit the android fastboot already? is it still a .bat file
osx, i already changed the file. what is apx mode? my adam has CWM on it, i understand that i am not supposed to have it for this HC rom. can i use the recovery image in the nvflash folder?
jakobdroid said:
osx, i already changed the file. what is apx mode? my adam has CWM on it, i understand that i am not supposed to have it for this HC rom. can i use the recovery image in the nvflash folder?
Click to expand...
Click to collapse
APX is the force recovery, the drivers are included with the NVflash, you must put your device into force recovery, with your device off you press volume down + power till you get your two lights to light up by the power cord, it'll be red and yellow, this is force recovery mode, I am using CW with it and I have listed above how to flash the CW with the increased partition. If you can't figure it out I will be adding the NVflash files with CW mode and non CW mode with the partition edits tonight. I will be turning the change log into a FAQ as well.
Just flashed the ROM and it is awesome. I was just wondering how to get a file managers working. I can't see my sd card. But otherwise, its amazing that honeycomb is up so fast.
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
jakobdroid said:
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
Click to expand...
Click to collapse
I'm downloading the file now, working on military lines so its slow to download but that way I can get a better idea of whats going on, also whats your operating system.
jakobdroid said:
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
Click to expand...
Click to collapse
Sounds like you're using linux like me. Are you on ubuntu. Cause I tried and tried and even with chmod and sudo and still got the same error. Consider this post though from: http://notioninkhacks.com/forums/viewtopic.php?f=90&t=1651&start=30
Hey gibson, thanks heaps for that! Actually, yourncomment before asking which folder I was in did it. Very strange, I had to run the commands from 2 folders above the extracted one, then symlink all the other files into the folder I was running from. Will post more later for people who run into similar issues, likely over at the unbricking thread. For now I've got a dualboot setup, and am running a minimal natty rootstock. I tried using the full omap4 image (ubuntu's default arm), but could only get it booting with lots of errors and no gui. Will be aiming to install the netbook desktop (unity 2d) in the next few days.
Re the post above, rayman's boot image already includes the kernel, so it's not needed in the rootstock command. Re the other options, probably will work, but remember rootstock is limited in what you can build... I.e., unless you have heaps of physical ram, you will probably only be able to build a few packages. Head over to xda, and the ubuntu on adam thread there for more info. We have experimented a lot with rootstock builds, and some of that might be useful.
Has anyone tried raymans boot.img with a natty rootstock? Did it work, and has anyone gotten a 2d unity gui up and running? My minimal natty rootstock boots fine, though I notice a few errors. Not sure if they are problematic or not. In any case, the build I made seems to be missing some important wireless tools, so I will likely rebuild it again with them in it soon. Am I likely to run into any problems using rayman's boot image, and steveh's kernel, with a natty build? Happy to post up my work if I get anything decent. Cheers.
osx 10.6.6, thank you!
jakobdroid said:
okay my adam is in apx mode, i did your steps for using CWM, but im still getting the error:
./nvflash: ./nvflash: cannot execute binary file
i used chmod on the download.sh file, as well as nvflash. any idea whats going wrong?
Click to expand...
Click to collapse
Also consider this: http://forum.xda-developers.com/archive/index.php/t-895388.html
Saved me some time thank you...
daiuton said:
Saved me some time thank you...
Click to expand...
Click to collapse
Don't know if the problem is solved yet but that doesn't take away from this honeycomb coolness. So happy to have so much use out of this Adam. Thanks.
that really didnt help, thanks though. i guess i will instal ubuntu in parallels and give it a shot...
Two problems here:
-How can i mount the adam with the computer? To move next updates and update in the next releases
-There is any gapps working (market,etc...)?

Help O2x bricked nvflash not working

Hi i recently tried to install a recovery from rom manager, but it installed one for g2x so then nothing could mount in recovery and when i tried to flash, something failed and now my device is bricked. I then found this guide http://forum.xda-developers.com/showthread.php?t=1229407&page=5 which i was able to recognise my device as a NVIDIA usb boot recovery drive but every time i press flash-recovery.bat and chose the partition, it says nvflash is not recognised as a command.... and whenever i press nvflash.exe itself, the cmd window appears for one second and it disappears. The package has all the drivers for nvflash but it doesnt friggin work. HELP
You need to flash an entire rom with nvflash, because you messed up the partition table (p990 and p999 have different partitions). With this guide you'll flash only the recovery...
After that you need to flash a proper baseband
Have you a g2x or an o2x?
iliatay said:
and whenever i press nvflash.exe itself, the cmd window appears for one second and it disappears. The package has all the drivers for nvflash but it doesnt friggin work. HELP
Click to expand...
Click to collapse
I have the same problem as him. Anyhelp?
I think you may try to reflash your device with the original firmware (KDZ file) which you can download from LG. Whole process is described in here:
http://forum.xda-developers.com/showpost.php?p=18946763
Please note that recently LG has changed something in their tools and now you have to "fool" them to do what you want them to. Please see this thread for details:
http://forum.xda-developers.com/showthread.php?t=1473781
Hope this will help you.
if it says that nvflash is not a recognised command, then edit the .bat to point to your nvflash.exe instead of just saying nvflash. (C:\path\to\your\nvflash.exe)
langhaardack said:
if it says that nvflash is not a recognised command, then edit the .bat to point to your nvflash.exe instead of just saying nvflash. (C:\path\to\your\nvflash.exe)
Click to expand...
Click to collapse
u can try this http://forum.xda-developers.com/showthread.php?t=1498021
i have tryed to ease the things to understand.
i had the same problem.
i downloaded these files:
http://uploaded.to/file/dkq74mlh
http://uploaded.to/file/2azotnvs
unpacked the files (important is that you put all files from the driver zip in one folder)
click volume + and volume - while connecting to your computer and it will recognize it
You go to device manager, right click on the apx ,update driversoftware, search on the computer for driver software, choose the folder you've put the driver files
then you can start flash.bat

LG GT540 Soft-brick Recovery

LG GT540 Soft-brick recovery
This tool will flash a CyanogenMod 6 rom (Android 2.2) has default but you can use the recovery images to do the job and change rom.
You must have Fastboot on your soft-bricked device.
I created a script (Windows only) and you can modify the script to change the recovery directory if required (Default is TWRP)
Thanks to the developers of the recoverys and the rom
Download link: https://dl.dropbox.com/u/33257225/Tweaks and Hacks/Android/LG GT540 Recovery/LG GT540 Recovery.zip
Unzip the file and start/modify the script
Has there is some confusion, this app will fix the non-booting issues like stuck on a certain screen like the LG Logo, bootloops etc.
Requirements: LG GT540 Drivers, Windows machine and fastboot
How to use: Download and extract the zip, put the device on fastboot mode, connect the device to the PC and then optionally, edit the batch file to your likings like the recovery images (There is plenty of images that come with the folder and has default, 'TWRP.img') and when your done, run the batch file
Update:
Version 0.6: Hopefully removed the space erase issue in the file causing the other issues and removed auto reboot-bootloader because the device would be soft brick and would not go to the system anyway. (Use the last link to update the updater script.) [Redownload batch file here: https://dl.dropbox.com/u/33257225/Tweaks and Hacks/Android/LG GT540 Recovery/LG_GT540_Recovery.bat or just redownload the zip if required.
Has promised, i said that there will be a Compact-Disc version with Installer, Updater and Cleaner, now its here!: http://dl.dropbox.com/u/33257225/Creations/LGGT540KITCD.zip
Installation: Download the file, extract the zip and then put it on a blank CD.
You may get an issue where you cannot enter the disc because of autorun, the workaround is to go to My Computer or just go to Compuer, Right click in the disc and then press Open
Link to download page with separated parts and scripts: http://caftp.pcsat.tv/lg_tools/ ​
This install a CM6 ROM on fastboot mode? i don't get it
leoposas said:
This install a CM6 ROM on fastboot mode? i don't get it
Click to expand...
Click to collapse
Go to fastboot mode then use the script, reboot* the device then after successfully booting to the CM6 rom, go to recovery to get the rom you want back.
Sent from my Sony Tablet S using xda premium
andyabc said:
Go to fastboot mode then use the script, renboot the device then after successfully booting to the CM6 rom, go to recovery to get the rom you want back.
Sent from my Sony Tablet S using xda premium
Click to expand...
Click to collapse
So this it's in case that you can't boot your rom?
leoposas said:
So this it's in case that you can't boot your rom?
Click to expand...
Click to collapse
Yes.
Sent from my Sony Tablet S using xda premium
I actually use this tool everytime a rom fails, good tool but i did not try flashing with the script (I made it today when i was bored after using the AIO toolkit odexing and resizing the rom that i use )
Sent from my Sony Tablet S using xda premium
would be useful for a phone where the boot (kernel) contains the recovery so everytime you flash a rom your recovery changes and when it fails you loose recovery. But for gt540 the recovery.img is independent...
-Grift- said:
would be useful for a phone where the boot (kernel) contains the recovery so everytime you flash a rom your recovery changes and when it fails you loose recovery. But for gt540 the recovery.img is independent...
Click to expand...
Click to collapse
That's what i though.
I made the script for ease of access, can someone try it out if it really works?
Just making sure i made this for a reason
Sent from my Sony Tablet S using xda premium
-Grift- said:
would be useful for a phone where the boot (kernel) contains the recovery so everytime you flash a rom your recovery changes and when it fails you loose recovery. But for gt540 the recovery.img is independent...
Click to expand...
Click to collapse
True
Sent from my Sony Tablet S using xda premium
Tool found broken and ends up putting phone to fastboot mode in every boot
Hopefully, someone can help me find out the issue has that the issue is causing errors to most of the parts like flashing
Did you try flashing 2.1 ROM with kdz via Download mode?
If the flash chip is "broken" you will not finish this one too, and the phone will need a service.
s-u-f-f-e-r said:
Did you try flashing 2.1 ROM with kdz via Download mode?
If the flash chip is "broken" you will not finish this one too, and the phone will need a service.
Click to expand...
Click to collapse
Yep, used to.
Sent from my Sony Tablet S using xda premium
Update Available!
Good news!: Compact-Disc version coming soon with an Updater, Autorun, Installation and Cleanup scripts!
Updater: This will use wget.exe in the extras folder to download the updated file (Check here for any new updates for the disc version or go to coolapps.host56.com/projects)
Autorun: You can now go straight to the flasher, you can still get into the disc for updates and stuff, just right-click and press open
Installation: This will get all the files into place for use for flashing :thumbup:
Cleanup: This will clearly (lol, did you see what i did there?) erase the android folder so you can reinstall it
This will only work on a CD, it has been set to drive E has set to default, you can grab the updater script for the stand-alone version but it will require "minor" modifications
CD Installation: Extract and copy files to your blank CD, then a reboot to get a knock on effect on the autorun (Make sure you have configurated the disc to act like a USB Flash Drive.)
This is a epic update so hopefully this is what you have been looking for
Ultimate update out!
Changelog:
ALL= Fixed the no such file or directory error, also in updater so if you have the CD version already, you can use the updater to do such task in two clicks to get the fixed version
New Update:
Changelog:
Fixed fastboot issue
Added adb for bootloader reboot
Fixed directory errors
Updater has been updated to a new update server (current one not from this update now does not work.)
-------------------------------------------------------------------------------------------------------
Use external site from the bottom of the first post to download the updated version of updater to update to the newest version of the main script.
-------------------------------------------------------------------------------------------------------
CD Version:
Updater fixed
Main script fixed
Original Version:
Main script fixed
-------------------------------------------------------------------------------------------------------
Dies it matter which kind if blank disc you use for this or is any specific best ie DVD or CD rw?? Probably a stupid question but not sure?
Sent from my ST25a using xda app-developers app
lismore said:
Dies it matter which kind if blank disc you use for this or is any specific best ie DVD or CD rw?? Probably a stupid question but not sure?
Sent from my ST25a using xda app-developers app
Click to expand...
Click to collapse
You can use any but make it act like "USB storage" or something, make sure you don't burn the files though.
When you get the files over run the installer (May want to right click and run has administrator if fails), everything is up to date anyway so you do not need to use the updater yet.
After using the installer, you can use autorun to run the script or enter C://android/ then double-click on the batch file (There is only one in that corrosponding folder). Just reminding even though I already said so in the first post o.o
Sent from my Sony Tablet S using xda premium
Update Available
Update Changelog:
Removed ADB bootloader reboot has in a soft brick situation you will not be able to use the system partition or/and boot partition.
Hopefully fixed space removal issues causing the batch not to work.
How to update:
CD version: Use the updater.
Portable version: Replace the main batch file for a new one manually.
--------------------------------------------------------------------------------------------
Because the drivers are not working on my PC and my device has been soft bricked, I cannot test it fully.​

Boot loop problem

Hello,
I tried installing a custom ROM on my 7310 and it had issues. I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop. I think I need to repartition, but when I click the repartition checkbox in ODIN I get an error.
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Thanks.
A few questions:
spazlon said:
I tried installing a custom ROM on my 7310 and it had issues.
Click to expand...
Click to collapse
What did you try to flash and how did you try doing it (CWM, ODIN, ...)?
What 'issues'?
I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop.
Click to expand...
Click to collapse
How far into the boot sequence does it get?
Are you able to get into recovery?
If so, what recovery do you have (Stock vs CWM)?
Have you tried seeing what is causing the boot-loop using adb?
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Click to expand...
Click to collapse
This is an action of last resort. Exhaust all other avenues first.
boscorama said:
What did you try to flash and how did you try doing it (CWM, ODIN, ...)?
What 'issues'?
Click to expand...
Click to collapse
I used CWM to flash AOSP 4.1.2. It seemed to work fine for a day or two, but then it needed charging (as normal). I let it charge over night and in the morning it had less battery. I figured the charger or cable were flaky so I tried another set on another outlet and same thing. Then it finally ran out of battery. I let it charge again over night and when I tried to turn it on it was really slow. The boot animation was only 1 frame every couple seconds. It would eventually boot all the way up, but it was still REALLY slow. So I went into CWM and reflashed the same ROM. Then I got a boot loop of the boot animation. I couldn't get into CWM any more, so then I went into download mode and flashed the official firmware and flashed it with ODIN.
boscorama said:
How far into the boot sequence does it get?
Click to expand...
Click to collapse
Now when I turn it on it just says, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I can flash again with ODIN and it will get to the Samsung boot animation and just pulse SAMSUNG.
boscorama said:
Are you able to get into recovery?
If so, what recovery do you have (Stock vs CWM)?
Click to expand...
Click to collapse
If I hold power and volume down I can get into download mode or Samsung recovery, not CWM, and power with volume up doesn't do anything.
boscorama said:
Have you tried seeing what is causing the boot-loop using adb?
Click to expand...
Click to collapse
I don't know anything about adb and I'm not sure what I would be looking for. Is there a tutorial I can follow somewhere?
Thanks for any help!
This worked for me with similar problem
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Thanks! I'll give this a try when I get home. I'll let you know how it works out.
Don't ever try to 'repartion unless you really know what you're doing. You're soft bricked. Repartion and you'll hard brick.
I'd go back and get hc from sammobile and flash that with Odin. Ics has had some problems.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
Don't ever try to 'repartion unless you really know what you're doing. You're soft bricked. Repartion and you'll hard brick.
I'd go back and get hc from sammobile and flash that with Odin. Ics has had some problems.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Agreed - my procedure avoids manual repartitioning - I tried lots of other procedures but none worked. I think my data partition had become corrupt because I kept getting error messages. My first try was to recover with my cwm recovery file I made originally but I kept getting back to the boot loop .
spazlon said:
Hello,
I tried installing a custom ROM on my 7310 and it had issues. I have tried installing the original ICS from the sammyfirmware site using ODIN. Now I have a boot loop. I think I need to repartition, but when I click the repartition checkbox in ODIN I get an error.
Do I need to repartition? If so, how do I do it? If not, how do I fix this error?
Thanks.
Click to expand...
Click to collapse
I always got something like that ...
After bootloop just go to recrovery mode then factory riset ... its 100% WORK
Sent from my GT-P7300 using xda premium
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
spazlon said:
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
Click to expand...
Click to collapse
Sorry - being a newbie myself I'm at a loss. It worked a charm for me.
spazlon said:
I followed the steps outlined by mobjunky and was able to get an official Honeycomb ROM installed, boot the official and copy my custom ROM and CWM 6.0.0.8 on it. Then install CWM 5.4.0.4 followed by 6.0.0.8.
Now my problem is that any custom ROM I put on there just does a boot screen loop. I tried CM10 and the latest AOSP. To install the ROMs I just booted into CWM, installed the ROM from zip, then installed the gapps. I've tried with and without formatting the cache, user data, and Dalkiv, same results.
What am I doing wrong? I have loaded tons of ROMs on this before without any issues, then all of a sudden I can't get anything except official loaded.
Click to expand...
Click to collapse
did a format /system before installing the custom roms? This is an important step.
prince93 said:
did a format /system before installing the custom roms? This is an important step.
Click to expand...
Click to collapse
This fixed it. Never had to do it with any of my other devices. CM10 loaded quickly after that. Loving how fast JB is!
Thanks!
Sent from my GT-P7310 using Tapatalk HD
It worked
mobjunky said:
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Click to expand...
Click to collapse
WOw! This fixed my Tablet! thank you ever so much!!
mjramos15 said:
WOw! This fixed my Tablet! thank you ever so much!!
Click to expand...
Click to collapse
mobjunky said:
Hi Spazlon,
Sorry I'm not allowed to post links yet as I am also very fresh. But I've underlined the addresses so you should be able to find them
I just spent the best of 2 days trying to solve a similar issue - my 8.9 P7300 kept running in boot loop. It had been running ICS stable for several weeks, then suddenly started to loop boot for no good reason. Anyway - you need two programs installed on your computer as well as USB drivers for your tablet. The two programs are Odin and SDK developer package. Odin3 v 1,87 and 1.85 are found here: filecrop.com/Odin-1.87 - try some of the links, one of them should work without having to type a password. The SDK is found here: developer.android.com/sdk You can find more about how to use the developer package on that site as well, but I installed as support for Android 2.1 through to 4.1
Also install the USB driver files for your tablet on your PC. For example from here: xpdrivers.com/usb/_1_24.cfm?gclid=CL2iDs7MCFWF7cAodxFYANQ
You also need the following recovery files which you can find by searching the developer forum for galaxy tab 8.9:
ClockworkMod_Recovery_v5.5.0.4.tar
P73xx_Stock_Recovery.tar
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and finally a ROM of your choice, for example the ICS rom cm-9-20121028-NIGHTLY-p5.zip that I just used. You can find the latest official ICS ROM's here get.cm/?device=p5
Now - hold down the volume down button on one of the boot cycles. You should now get into a menu with two choices - Download and Recovery. Default is "Download" - if you press volume down you switch between the two choices. Press volume up to select the choice you want.
First you want to select the "Download" option. Then connect your tablet to your PC. The drivers should now install and your tablet should read that you are connected.
Now start Odin3. Click the PDA button and select your P73xx_Stock_Recovery.tar file. Then press Start.
Once finished the tablet will reboot, and you now need to once again get into the recovery menu. Now select the recovery option, not the download menu. You get into the stock recovery menu where you navigate with the volume buttons and select choices with the power button. Do a full factory reset and wipe the cache. WARNING - you will loose ALL your data, but it'either that or stick to a bricked tablet so.... You will also loose your root access,m which is why the next step is needed.
Now that everything is wiped clean you can use Odin again in "download mode" to install ClockworkMod_Recovery_v5.5.0.4.tar with the same procedure as before. You now have root access.
Reboot again and once again into the recovery mode (not download mode). Once you get into the CWM recovery menu you are ready for the final step, which is to install your new operating system.
Go to your SDK installation folder and find the folder named "platform-tools".
First you want to copy two files into this folder (provided you want to install Cynaogen Mod 9):
Clockwork_Recovery_6.0.0.8_GT-P7300.zip
and
Your ROM file of choice
Press shift and right-click in that folder and select "Open command window here". In the command prompt write
adb shell
Note - I had some problems here which was caused by lack of permissions. On your tablet in the CWM menu there should be a choice under the advanced menu for fixing permissions. Use that and you should be able to get into the terminal shell afterwards with the adb shell command
Now write the following command sequence:
• mount /data (don't worry if you get an error message - it means the folder is already mounted)
• cd /data
• mkdir media (if you get an error message saying the folder already exists, that's also OK!)
• exit
• adb push Clockwork_Recovery_6.0.0.8_GT-P7300.zip /data/media
Now you may have to wait a little while until your command prompt is back confirming that the file was uploaded.
Now on your tablet go to the menu point "install zip from sdcard" and find your CWM file that you just uploaded and run that.
Reboot once again into the "recovery mode" - we are now nearly finished.
Run the above push command again from the computer terminal window, this time to upload the ROM file you want to install. (the command is adb push [filename].zip /data/media)
Now on your CWM recovery menu once again run the zip file you just uploaded from the "install zip from sdcard" menu
When completed and you now reboot you should have a completely fresh android installation. Hope this helps.
Remember to mark this thread with solved if it works!
Thanks to kallt_kaffe and all the others who helped me through their various posts (hope that coffee isn't getting too cold again), as well as the following web sites that indirectly helped me resolve this issue googleymind.com/2011/11/guide-so-you-think-you-bricked-your.html#.UJUNN8XAd8G and galaxytabhacks.com/galaxy-tab-10-1-hacks/how-to-root-galaxy-tab-10-1-the-easy-way/
Good luck.
Click to expand...
Click to collapse
Gee thanks. This saved my tab. I'd almost given up on it and then voila.

Need help. Cannot recovery after ICS update attemp.

Hi guys,
I tried to update my 2x from 20e to ICS today but it was unsuccessful (http://forum.xda-developers.com/showthread.php?t=1959545). I tried to do recovery from the CMW as recommended but it fails. Error/ mounting system. When I reboot its stuck on LG logo. I have tried do recovery using NVflash but not successful either (http://forum.xda-developers.com/showthread.php?t=1975274&page=5).
My previous setting: v20e. CWM 5.0.2.7.
Its been months since my last update for the 20e. I am not sure I am on the right driver. CMW version etc. and I have just use win7 from vista last two months. I am not sure if that affect too.
Any help are much appreciated. Thanks in advance.
Use nvflash to flash cm10 (old BL) and then recover nandoid
Sent from LG 2X using Tapatalk 3 Beta
Rayman96 said:
Use nvflash to flash cm10 (old BL) and then recover nandoid
Sent from LG 2X using Tapatalk 3 Beta
Click to expand...
Click to collapse
I have downloaded Homero2 nvflash. tried to follow the instruction. When I open the nvflash I dissapear as soon its open. Any step missing?
It should just open right? Sorry for my noob question, what is nandroid? I am on win7
ary820 said:
When I open the nvflash I dissapear as soon its open. Any step missing?
It should just open right?
Click to expand...
Click to collapse
Do you click on the batch file, or on the nvflash .exe file? You should use the batch file, not the .exe. Also, open command prompt first, and run the batch file from there -- you will see all the errors and other messages. (I should probably put this in my signature, as I already mentioned it probably half a dozen times in different topics...)
what is nandroid?
Click to expand...
Click to collapse
It's the backup that you create in CWM.
ary820 said:
Hi guys,
I tried to update my 2x from 20e to ICS today but it was unsuccessful (http://forum.xda-developers.com/showthread.php?t=1959545). I tried to do recovery from the CMW as recommended but it fails. Error/ mounting system. When I reboot its stuck on LG logo. I have tried do recovery using NVflash but not successful either (http://forum.xda-developers.com/showthread.php?t=1975274&page=5).
My previous setting: v20e. CWM 5.0.2.7.
Its been months since my last update for the 20e. I am not sure I am on the right driver. CMW version etc. and I have just use win7 from vista last two months. I am not sure if that affect too.
Any help are much appreciated. Thanks in advance.
Click to expand...
Click to collapse
reflash or flash it using nvflash!!
kt-Froggy said:
Do you click on the batch file, or on the nvflash .exe file? You should use the batch file, not the .exe. Also, open command prompt first, and run the batch file from there -- you will see all the errors and other messages. (I should probably put this in my signature, as I already mentioned it probably half a dozen times in different topics...)
It's the backup that you create in CWM.
Click to expand...
Click to collapse
Thanks for the feedback..how do I run batch file from command prompt?
Isit goto window-->cmd-->type: c:\nvflash\nvflash? I have created the "nvflash: folder in C.
Back to the source, I tried to follow as the instruction:
-Download the attached file and unzip it. The pack includes the APX driver (folder driver)
1.- Remove the battery to the phone.
2.- Press and hold Vol- and Vol+ and without releasing the 2 keys connect the USB cable to the PC
3.- Go to the NVFlash folder and run:
3a.- Windows should detect a new device APK, cancel the installation and install the driver which includes the ROM.
3b.- On Linux not ago missing driver.
4.- Browse to the folder where you unzipped the RAR and typing CMD in the breadcrumb bar, Linux opens the console.
- Type:
Windows
Code:
flash.bat
When I extract the file, the driver folder amd64 folder, i386 folder and nvidiausb file. I didn't see APX folder/file.
I am not clear abot step #3 open nvflash & run: (I am not sure what to run)
# How to go about in step 4? This is what I have tried. Go to the folder, type cmd, then type "flash.bat"
I see this:
c:\nvflasf>echo "flashendo lg optimus 2x" flashendo lg optimus 2x......
c:\nvflasf>nvflash.exe --bct star.bct --bct -- configfile android_fastboot_emm
c_ful.cfg - create -- bl.fastboot. bin -- go
Nvflash started
rcm version 0x20001
command send failed (usb write failed)
c:nvflash\ scho "listo!" listo!
Need help, I am sure where I do wrong.
Update: Somehow I made the recovery, same procedure as above. (Big thanks to Homero2 for the tools)
I wanna ask some question:
1-I have redo the ICS update (ICS extended by TonyP and Harsh). I encounter same problem as before (error 7). Any tips where might go wrong or what I should check before flashing.
2-Where I can flash from here (from Homero2 ROM)? GB only or I can flash to ICS or JB?
3-I try update the ROM manager via google play..but I think its only 5.2.0.7 version. Does higher version (v6) for ICS and do I need to do recovery before flashing via ROM manager?
Thanks in advance.

Categories

Resources