The Good:
I used the unlocker, and installed clockworkmod from fastboot.
The Bad:
Mistake 1: I was not logged into a google account when I used the unlocker. When the device boots, it says that it is unlocked in the top left, but I can't shake the feeling that it was not done correctly,
Mistake 2: I did not make a backup. I was coming off a factory reset, and figured I had no app data to protect, so why do a backup? I followed some instructions I found on the net, did some cmd: commands on my computer, and BAM: Clockwork Mod.
Mistake 3: When I could not get a rom to load in CWM, (would not detect update.zip), I started looking for fixes all over. Root Checker said I was not rooted. I tried using an APK to root that I found in a forum, that did not work either. The exploit involving using an app backup did not go through for me.
Mistake 4: In an attempt to get rid of Mistake 1, I thought "why not do a factory data reset?". Now, my Transformer prime only boots into CWM. I am sitting here looking at v5.8.2.0.
Any time I select "reboot system now", I end up back here.
I realize that as a total noob, I do not deserve the kindness of this forum, however, any mercy/help that you give me will give you several karma points.
Please help.
Any links you can provide will not just help me, but any additional noobs that are dumb enough to do what I did.
Mistake 1: google account has nothing to do with unlocking. If you have fastboot access you're unlocked! so forget mistake 1 and 4
Mistake 2: no comment except that i don't understand what instructions you followed from the net, the cmd part... A backup is performed within CWM ... Nevertheless you're bricked so it isn't very important.
Mistake 3: a big mess in your head. If you just unlocked and flashed cwm it's logical that you are not rooted in your ROM. CWM has nothing to do or care with root !! CWM is totally independant from the ROM, it has by default root power as it runs froms a different partition and deals with /system and /data etc from 'outside'.
You gain root by either flashing a custom ROM (they are all rooted) or flashing the super user itself only (SU.zip).
Mistake 4: don't use cwm on that device.
Mistake 5: you are a monkey typer.... STOP trying every crap you find 'on the net' ! You seem to have quite blurred knowledge of what is an android device, so be extremelly carefull or you'll end with a real hard bricked prime.
Prime is very specific, don't use things that have not been designed specifically for it.
You are in recovery bootloop, see in dev section the unbrick thread (in stickies threads), option 1a.
Don't use cwm.
Use TWRP.
big time noob said:
The Good:
I used the unlocker, and installed clockworkmod from fastboot.
The Bad:
Mistake 1: I was not logged into a google account when I used the unlocker. When the device boots, it says that it is unlocked in the top left, but I can't shake the feeling that it was not done correctly,
Mistake 2: I did not make a backup. I was coming off a factory reset, and figured I had no app data to protect, so why do a backup? I followed some instructions I found on the net, did some cmd: commands on my computer, and BAM: Clockwork Mod.
Mistake 3: When I could not get a rom to load in CWM, (would not detect update.zip), I started looking for fixes all over. Root Checker said I was not rooted. I tried using an APK to root that I found in a forum, that did not work either. The exploit involving using an app backup did not go through for me.
Mistake 4: In an attempt to get rid of Mistake 1, I thought "why not do a factory data reset?". Now, my Transformer prime only boots into CWM. I am sitting here looking at v5.8.2.0.
Any time I select "reboot system now", I end up back here.
I realize that as a total noob, I do not deserve the kindness of this forum, however, any mercy/help that you give me will give you several karma points.
Please help.
Any links you can provide will not just help me, but any additional noobs that are dumb enough to do what I did.
Click to expand...
Click to collapse
Okay so you messed up... slightly... no big deal... here is what you do..
From the sounds of it you have no rom atm... no big deal... download a rom.. i suggest blackbean or eos...
blackbean found here... http://rootzwiki.com/index.php?/topi...ackbean-(8-15)
eos found here.. http://forum.xda-developers.com/showthread.php?t=1782413
Download and install http://forum.xda-developers.com/showthread.php?t=1426502 naked drivers.... follow the instructions...
I prefer blackbean... anyways.... now download nvflash from here http://androidroot.mobi/?p=452
Unzip the file.. put your rom where you find adb.exe shoudl be in C:\nvflash\tf201_nvflashpack if you put the file in C:
*******Now.... boot to recovery... connect tab to the pc.... with the windows open (nvflashpack) clcik in the window... press and hold shift button the right clcik mouse and select open command prompt here... this should give you the command prompt.
Now copy this adb devices right click in the command prompt window and paste... press enter... you should see your transformer...
now type adb push /name of rom you downloaded .zip/ sdcard
This should push the rom to your tab... it will take about 5 minutes be patient....
Install the zip through cwm....
Now there is a chance this does not work.. don't worry... if it doesn't work .. go here ....http://forum.xda-developers.com/showthread.php?t=1615990 this is twrp.... download then follow the fastboot install instructions
At this point you probably want to follow the nvflash instructions to install the custom bootloader since twrp says it needs it... go back here and follow instructions... http://forum.xda-developers.com/showthread.php?t=1774352
start again from ******now boot to recovery....
After you accomplish this, you should complete the nvflash instructions and make your backups...
Yes it does seem like a lot... but unless you want to sell me a paper weight for $5 you need to complete this... if you need further assistance write here or pm me..... good luck Luke... may the force be with you...
A helpfull answer without trolling? really.. Whats this world coming to!!
anyway.. I added a "thank you" even though I didnt brick my prime ( yet )
johanjonker said:
A helpfull answer without trolling? really.. Whats this world coming to!!
anyway.. I added a "thank you" even though I didnt brick my prime ( yet )
Click to expand...
Click to collapse
Your welcome ... I think.... did I get you out of a jam?
I dont troll I try to help people from what i have experienced..... I myself have made some questionable decisions.... just figure since I have learned from them .. no reason to make others suffer through needless anxiety......
big time noob said:
The Good:
Mistake 3: When I could not get a rom to load in CWM, (would not detect update.zip), I started looking for fixes all over. Root Checker said I was not rooted. I tried using an APK to root that I found in a forum, that did not work either. The exploit involving using an app backup did not go through for me.
Click to expand...
Click to collapse
The others already answered everything else, but here I'm wondering if it's not just a simple mistake.
If I remember correctly, there are 2 options in CMW to flash a zip file : either an update.zip file which has to be in a specific directory, or choose the file from the storage.
My guess is that you tried the first option which returned an error because you don't have an update.zip file.
Have you tried browsing to the ROM file manually?
Besides that, you might want to setup NVFlash on your device (be sure to ask for help in the NVFlash thread if you have any doubt about one of the steps, so you don't end up with a brick).
The NVFlash thread is here : http://forum.xda-developers.com/showthread.php?t=1774352
Since you don't seem to understand Android very well, having NVFlash would at least protect you from most (if not all) software bricks in case you make a bigger mistake like flash an Official Asus ROM on your unlocked device..
Hopefully this will help.
Mithrandir007 said:
The others already answered everything else, but here I'm wondering if it's not just a simple mistake.
If I remember correctly, there are 2 options in CMW to flash a zip file : either an update.zip file which has to be in a specific directory, or choose the file from the storage.
My guess is that you tried the first option which returned an error because you don't have an update.zip file.
Have you tried browsing to the ROM file manually?
Besides that, you might want to setup NVFlash on your device (be sure to ask for help in the NVFlash thread if you have any doubt about one of the steps, so you don't end up with a brick).
The NVFlash thread is here : http://forum.xda-developers.com/showthread.php?t=1774352
Since you don't seem to understand Android very well, having NVFlash would at least protect you from most (if not all) software bricks in case you make a bigger mistake like flash an Official Asus ROM on your unlocked device..
Hopefully this will help.
Click to expand...
Click to collapse
Very valid point Mithrandir007.... just to be cleear when following the nvflash instructions.... follow step by step.... all the way to the end..... from this thread http://androidroot.mobi/t3_nvflash/ dont stop until you see the statement ... coming soon... then you are actually done....
Thanks
Thank you guys for your help, and not being too hard on me...except maybe the first guy.
I will try those things when I get back from work.
Seriously...
Gage_Hero said:
Okay so you messed up... slightly... no big deal... here is what you do..
From the sounds of it you have no rom atm... no big deal... download a rom.. i suggest blackbean or eos...
Download and install naked drivers.... follow the instructions...
I prefer blackbean... anyways.... now download nvflash from here
Unzip the file.. put your rom where you find adb.exe shoudl be in C:\nvflash\tf201_nvflashpack if you put the file in C:
*******Now.... boot to recovery... connect tab to the pc.... with the windows open (nvflashpack) clcik in the window... press and hold shift button the right clcik mouse and select open command prompt here... this should give you the command prompt.
Now copy this adb devices right click in the command prompt window and paste... press enter... you should see your transformer...
now type adb push /name of rom you downloaded .zip/ sdcard
This should push the rom to your tab... it will take about 5 minutes be patient....
Install the zip through cwm....
Now there is a chance this does not work.. don't worry... if it doesn't work .. go here .... this is twrp.... download then follow the fastboot install instructions
At this point you probably want to follow the nvflash instructions to install the custom bootloader since twrp says it needs it... go back here and follow instructions...
start again from ******now boot to recovery....
After you accomplish this, you should complete the nvflash instructions and make your backups...
Yes it does seem like a lot... but unless you want to sell me a paper weight for $5 you need to complete this... if you need further assistance write here or pm me..... good luck Luke... may the force be with you...
Click to expand...
Click to collapse
I ask this next question with a scared expression on my face...what if the TF201 is not taking a charge now?
Last night it would boot into clockworkmod, and I did not plug it in, so it just sat there burning battery in clockworkmod screen.
Today, I go to plug it into the usb, and I briefly get the screen that shows the battery in the red, then it fades out.
I am going to try plugging it into the wall when I get home, but I am scared that I might not get the chance to fix my device.
It comes vaguely in my mind that I read something about cwm not supporting charging but I'm not sure.
If the battery is drained completely it will need several minutes with wall charger to come back to life.
You are really messed up. Download a Rom from development section.. put it in your Sdcard.
First plug your phone to charger.. let it charge for an hour.
When your mobile switches ON.
Enter CWM recovery or anyone you have.. go to mount option, wipe everything except sdcard. Go to advance and wipe dalvik cache.. then go to Install zip from sdcard option in it.. select the downloaded file.
big time noob said:
I ask this next question with a scared expression on my face...what if the TF201 is not taking a charge now?
Last night it would boot into clockworkmod, and I did not plug it in, so it just sat there burning battery in clockworkmod screen.
Today, I go to plug it into the usb, and I briefly get the screen that shows the battery in the red, then it fades out.
I am going to try plugging it into the wall when I get home, but I am scared that I might not get the chance to fix my device.
Click to expand...
Click to collapse
Some usb connections don't charge... my pc at work is like that.... or they charge so little that it barely makes a difference. Plug it into the wall for at least a hour... preferably longer since you are going to be doing things that may not work out so well if the battery dies in the middle of things.... Also given how frail the charger socket is, unless you have it sitting on a flat surface, I wouldn't attempt doing the work while it is plugged in... Would want you to get the software fixed and you bust up the charging socket or cable...
Prime needs 15 volts to charge, USB only delivers 5, so it's discharging while plugged to an USB most of the time.
Don't know how to fix your CWM problem but I do know the Prime will charge on a USB port if it's turned off. It does take a very long time though.
From the TF201 manual:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Might help
Mithrandir007 said:
The others already answered everything else, but here I'm wondering if it's not just a simple mistake.
If I remember correctly, there are 2 options in CMW to flash a zip file : either an update.zip file which has to be in a specific directory, or choose the file from the storage.
My guess is that you tried the first option which returned an error because you don't have an update.zip file.
Have you tried browsing to the ROM file manually?
Besides that, you might want to setup NVFlash on your device (be sure to ask for help in the NVFlash thread if you have any doubt about one of the steps, so you don't end up with a brick).
The NVFlash thread is here : http://forum.xda-developers.com/showthread.php?t=1774352
Since you don't seem to understand Android very well, having NVFlash would at least protect you from most (if not all) software bricks in case you make a bigger mistake like flash an Official Asus ROM on your unlocked device..
Hopefully this will help.
Click to expand...
Click to collapse
Thanks for the response. On the nvflash page it says NOTE: THIS REQUIRES A NON-BRICKED AND UNLOCKED DEVICE. IT WON'T WORK ON ALREADY BRICKED DEVICES
Does that mean me? If so, I might be stuck.
I tried installing with the update.zip option, didn't work. I also tried installing by browsing, but weirdly, it does not give me the options of any of the roms I have on the SD card...when the prime was stock, it saw the files on the SD card, but now it just shows me options of several folders that do not actually exist, a couple of subfolders, but no actual files or zip files.
When I boot (holding the power and down volume button) The message basically says, The device is unlocked, Android cardhu-user bootloader. Says something about the version I was running, .28, and that it is looking for an ota update. At the bottom, it says booting recovery kernel image. Then it loads clockworkmod.
I installed the naked drivers, so I can now see the Android ADB interface on my windows device manager. I cannot see the device as one of the drives from windows explorer.
I hope that info helps. What do you think? How screwed am I still?
rr0yy said:
You are really messed up. Download a Rom from development section.. put it in your Sdcard.
First plug your phone to charger.. let it charge for an hour.
When your mobile switches ON.
Enter CWM recovery or anyone you have.. go to mount option, wipe everything except sdcard. Go to advance and wipe dalvik cache.. then go to Install zip from sdcard option in it.. select the downloaded file.
Click to expand...
Click to collapse
The options I get there are:
format system
format cache
format staging
format data
Which one do I pick? All of them?
big time noob said:
The options I get there are:
format system
format cache
format staging
format data
Which one do I pick? All of them?
Click to expand...
Click to collapse
Nope.. none of them.... in cwm you have update from zip... or install zip file (or something like that) you want the one that doesn't say update.....
big time noob said:
The options I get there are:
format system
format cache
format staging
format data
Which one do I pick? All of them?
Click to expand...
Click to collapse
Nope.. none of them.... in cwm you have update from zip... or install zip file (or something like that) you want the one that doesn't say update.....
The image is from 5.5 but it says install zip from sdcard... if you adb push the rom there you will be able to install...
Gage_Hero said:
Nope.. none of them.... in cwm you have update from zip... or install zip file (or something like that) you want the one that doesn't say update.....
The image is from 5.5 but it says install zip from sdcard... if you adb push the rom there you will be able to install...
Click to expand...
Click to collapse
2 things:
1. I cannot see the sd card in the mount/unmount area of CWM. I feel like this is a big part of my problem.
2. The instructions I see for nvflash involve fastboot. I could be wrong, but if I cannot get to the fastboot screen on my prime, how can I run the fastboot command lines? I can only get to the cwm screens.
Gage_Hero said:
Nope.. none of them.... in cwm you have update from zip... or install zip file (or something like that) you want the one that doesn't say update.....
The image is from 5.5 but it says install zip from sdcard... if you adb push the rom there you will be able to install...
Click to expand...
Click to collapse
Attached 2.1.2 twrp....give it a go....
Related
I know there are threads about this but none helped me. I rooted my phone the other day but i cant figure out how to set up adb. under my androidsdk folder it says adb is in there. but whenever i type it in the command spot no serial number comes up for my phone and when i try the manual part it doesnt work.. i was following the Unlocker tutorial.. please help i want ROMS!
did you install the adb driver from htc?
http://androidforums.com/all-things-root-eris/53963-guide-stock-1-5-latest-root-2-1-a.html
There's the address for the guide that I followed. Its extremely easy, just follow the instructions closely.
Thanks! i tried that b4 and it didnt work i guess i messed up before.. Thanks a lot
Hey there. I had run into a similar situation the first time I tried to root my phone. I tried a bunch of different tutorials and they all just ended up giving me a headache. I THINK I used the unlockr.com tutorial first and I ended up installing a leak version of 2.1 which made me unable to actually root the phone. I hope that isn't the case and I can't be 100% certain since I tried doing this a few different ways from a few different sites. The best way to check this is to go to your settings and look at the About Phone section and check to see if your version of 2.1 says release-keys or test-keys. Release-bad, test-good. If you have release-keys then your best bet is waiting till they finally figure out how to root that version. The devs have been working on it for a long time and I think they are losing ambition, but there is still a glimmer of hope. If you have the test keys version, then you should be good and probably just misspelled something in setting up the adb/changing to the right directory, or in making sure you have the latest USB drivers, have USB debugging on, have your phone on charge only (not disk drive), etc.
everything worked well until i tried to load the evil eris rom i put the zip file in my root folder and when i wiped my phone then tried to load it it said load aborted... any ideas?
es0tericcha0s said:
Hey there. I had run into a similar situation the first time I tried to root my phone. I tried a bunch of different tutorials and they all just ended up giving me a headache. I THINK I used the unlockr.com tutorial first and I ended up installing a leak version of 2.1 which made me unable to actually root the phone. I hope that isn't the case and I can't be 100% certain since I tried doing this a few different ways from a few different sites. The best way to check this is to go to your settings and look at the About Phone section and check to see if your version of 2.1 says release-keys or test-keys. Release-bad, test-good. If you have release-keys then your best bet is waiting till they finally figure out how to root that version. The devs have been working on it for a long time and I think they are losing ambition, but there is still a glimmer of hope. If you have the test keys version, then you should be good and probably just misspelled something in setting up the adb/changing to the right directory, or in making sure you have the latest USB drivers, have USB debugging on, have your phone on charge only (not disk drive), etc.
Click to expand...
Click to collapse
it says test keys thank god ha. i had to use other youtube videos to figure it out. now i just have problems with the roms
fenwaynomar45 said:
everything worked well until i tried to load the evil eris rom i put the zip file in my root folder and when i wiped my phone then tried to load it it said load aborted... any ideas?
Click to expand...
Click to collapse
Hmm... "put the zip file in my root folder"
1. You want to copy the zip file to the "root" of your sdcard. That means it is on the sdcard, but not in any folders.
2. Then boot into Recovery (Hold volume up + power on)
3. Then select flash zip from sdcard.
4. Then choose the zip of the rom you want.
5. When finished reboot.
6. Then sit back and wait for it to finish. You should be good to go.
g00gl3 said:
Hmm... "put the zip file in my root folder"
1. You want to copy the zip file to the "root" of your sdcard. That means it is on the sdcard, but not in any folders.
2. Then boot into Recovery (Hold volume up + power on)
3. Then select flash zip from sdcard.
4. Then choose the zip of the rom you want.
5. When finished reboot.
6. Then sit back and wait for it to finish. You should be good to go.
Click to expand...
Click to collapse
thats exactly what i did.. im gonna try another rom and see what happens
Ivan seems to be working fine but when i tried evil eris it immediately goes to aborted
fenwaynomar45 said:
Ivan seems to be working fine but when i tried evil eris it immediately goes to aborted
Click to expand...
Click to collapse
Which version of Evil Eris did you try?
believe it was the 3.0
fenwaynomar45 said:
believe it was the 3.0
Click to expand...
Click to collapse
Try and download the file again. Probably just a corrupted download...
ill try it now im going to mess around with ivan right now since im just happy to have something ha
There's the video, guys.. have fun and be careful!
written instructions are as follows:
OK! so you've decided to take on the menial task of installing a custom rom, to make your mytouch... well for lack of a better term, YOURS! If you've had a G1 or a Mytouch 3g in the past, as I have, then the process is much the same..
Step 1
Download your rom from the website to your computer *durrrrrr* also make sure your device is in normal operating mode, and also download the update.zip for clockwork recovery if you dont already have it from HERE
Step 2
Copy the rom and update.zip for clockwork from your computer to your phone's SD card root directory, also known as /sdcard
Step 3
Power off phone
Step 4
Power onto Fastboot mode with Volume Down button and Power
Step 5
Get into recovery mode by pressing volume down once fastboot loads, and then power to select
Step 6
Once in recovery basic mode, where you see the triangle with red exclamation, hold volume up and press power again
Step 7
While in recovery mode, hit volume down to get to apply update.zip which will put you in clockwork recovery as long as the update.zip for clockwork recovery is on your sd card
Step 8
After applying your update.zip, you're going to scroll down to install zip from sd card using volume down button and then power to select
Step 9
Once again, go to install zip from sdcard and press power
Step 10
Select your zip in the menu, then press power
Step 11
Wait for zip to install and hope to hell the zip is signed correctly and not damaged
Step 12
After zip installs, back out to main menu and reboot phone!
Step 13
Wait for Rom to load 100%.. WATCH YOUR LOGCAT TO VERIFY NO BOOTLOOPS!!!
Done!!
If you download "QuickBoot" from the market you can boot directly to "Recovery" bypassing the bootloader.
Re: [how-to] put a custom rom on your slide!!!
I'm assuming this is a tutorial for future rom releases, correct?
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
well there's already 2 out at this time, with slideroot2 and the legend rom.. there will be tons more, i'm sure.. so yeah, this is a generalized install procedure for such things
I like the addition of the ADB & logcat steps! Nice touch, man...
heh thanks i want users to be able to see what they did and begin to learn how to fix future mistakes lol
I love the legend ROM but I needed the keyboard one night so I switched to slidemeroot2.
Any chance for Keyboard lights coming?
Also, couldn't load titanium backup in the legend. Any suggestions there?
to get titanium to load right, you have to install a different superuser.apk than the one that's stock. i dunno why exactly. also, legend is a BETA so it'll be updated soon by eugene, it is by no means a final version
Thank you. It is a pretty sweet beta.
Hate to state the obvious, but you should mention that this requires your MT3G Slide to be rooted... you know peeps will come out the wood works asking "why cant I do this!"
ummmm fermunky, why not watch video at 0:15 through 0:25?
kingofyo1 said:
ummmm fermunky, i would suggest rewatching the first minute of the video... that should fix your thoughts about what i've said
Click to expand...
Click to collapse
Touche my friend, I didn't even watch the video, since I am not rooted yet anyways , but you know some people will still attempt to follow your directions and not watch the video Not everyone has good intuition
lol its cool man... if you're anywhere close to gulfport ms or are willing to drive here, i'll root your slide and eng build and legend it for free...
kingofyo1 said:
lol its cool man... if you're anywhere close to gulfport ms or are willing to drive here, i'll root your slide and eng build and legend it for free...
Click to expand...
Click to collapse
Wish I could, but I am waiting daily at the beaches of St Pete to catch the tar balls coming in!
fermunky said:
Wish I could, but I am waiting daily at the beaches of St Pete to catch the tar balls coming in!
Click to expand...
Click to collapse
LOl you gonna manufacture yourself some gasoline??
serialtoon said:
If you download "QuickBoot" from the market you can boot directly to "Recovery" bypassing the bootloader.
Click to expand...
Click to collapse
Does this mean that I don't have to root first to flash roms? Can i boot to recovery and flash to eugene's already rooted rom?
once you downgrade to the eng build, you can flash any rom for the slide... you have to root and then flash that downgrade though before you can do anything to it
When will a permanent recovery flash come available? Only a minor inconvenience since it only is two extra steps using the stock recovery... well three including copying the update.zip over.
whenever the spl comes, is when it comes i dont have a date/time for ya, devs are working on it... i know one in particular made a bit of progress yesterday, so we'll see what happens when it happens
Ok, I tried to install the SlideM ROM and and ran into an issue I'm not really sure how to fix.
I followed your video and instructions to the letter but on reboot the phone stopped at the first T-Mobile flash screen and froze. Using adb devices I come up with this;
C:\androidsdk\tools>adb devices
List of devices attached
HT069PS00585 offline
HT069PS00585 device
C:\androidsdk\tools>adb reboot
error: more than one device and emulator
...and the phone is locked onto that first t-mobile screen. I tried adb reboot, adb reboot-bootloader and still get nothing, even tried a hard reboot by pulling the battery to get to recovery mode and re-installed starting from step 1.....really hoping I didn't brick it. Any thoughts on why it happened or how I can go about fixing it?
***UPDATE*** went back and tried a method found in another thread, i.e., wiped data using Android recovery mode instead of Clockwork recovery, then re-installed SlideM. Worked perfectly on the first try
This is how to root and install a custom ROM on the Samsung I5500 mobile phone. I believe this may work on other Samsung handsets like the I5503 and I5508 but the I5500 is the only handset I have unlocked with the following tutorial.
I have tested this method using a new G5 in December 2011 but please understand that neither I nor the publishing website will take any responsibility for damage that may occur to your phone if you choose to follow this procedure and something goes wrong.
Firstly I’d like to thank JC_Master and CLShortFuse from XDA Developers and psyke83 from the ever informative MADTEAM for their work to make this possible.
There are a few different ways of doing this and I think I have tried them all, some resulting in a dead phone, some that just don’t work and some that are badly explained. This method has been tried and tested by myself and I will do my best to tutor it as simply as I can so that even a novice computer user may successfully flash / de-brand their phone from the putrid Samsung software!
OK, you ready?
Step 1
1.1 We need to install a boot-loader as the Samsung one is very limited and just plain awful! That said, it wasn’t intended to be used for anything other than the Samsung software so it’s not awful from their point of view but it’s pretty unfriendly to us.
1.2 If you know what a boot-loader is then skip to 1.3. A boot-loader is like a computers BIOS menu. If you have ever noticed when you turn on your computer there is some written text displayed (usually ‘Press F2 or DEL to enter Setup’) before it starts to boot Windows or whatever operating system it uses. If you push F2 or DEL when your computer tells you that you can you will go into a control interface that has options that you can set to tell your computer what to do when it is turned on and how to do it. Most computers are set to boot from the hard-disk first which is why yours starts to load your operating system. Many mobile phones work in the same way and the boot-loader (or BIOS) that we need to install will give us options to install our new ROM, to backup our phone data, to root it (gain entry to the system files – like being able to enter your ‘C:’ hard disk in Windows) and much more that the Samsung boot-loader will not.
1.3 Fortunately for us there is a clever bunch of people over at clockworkmod.com that have released a nice boot-loader for us that is just the job. They make these modded software files for us for free so please do donate something to them if you use their software so they can continue their work. Create a new folder called Samsung in your computers (C hard disk drive by left clicking Start Menu, Computer (or My Computer), double left click (C, right click (not on a file or icon) select New, Folder, type Samsung and the double click the folder to open it. Now resize the folder so it is not using the whole screen or minimize it but don’t close it. If you do close it, you know where it is! ‘C:\Samsung’
1.4 Download ClockworkMod-Galaxy5-v0.5 (Click the link) and SAVE it to your ‘C: \Samsung’ folder. For non I5500 mobile phones find your boot-loader here
1.5 Now let’s get the nice new Android ROM and its latest hotfix too. Remember to donate here as these boys have got to eat too! Download update-cm-7.1.0-galaxy5-v1.7.2-MADTEAM-signed.zip and v1.7.2-hotfix1.zip SAVE to your ‘C: \Samsung’ folder.
1.6 Once this is all done we can install an app from the ClockworkMod team called ‘ROM Manager’ which will allow us to recover, backup and restore our phone. Download it now to the same folder and we’ll do that last ROM Manager APK
1.7 Lets also get the latest Google applications pack to install later too gapps-gb-20110828-signed.zip
1.8 **Ignore this step** In order to write any new information to the phones system files we need to get permission to do so and Samsung don’t give you this permission, this is known as ROOT access. There are many installable applications for the G5 that claim to root your phone but the only one I have found that works is Super One Click. This is a Windows installed based program (.exe) and not an APK (.apk – Android phone installed application). Download it here SuperOneClick usual folder!
1.9 Next we need to download and install the Samsung USB drivers. If you have Samsung Kies running then stop or disable it. If you don’t know what I mean then don’t worry about it! Download SamsungUSB to anywhere on your PC and double click it to install it.
1.10 We now need ODIN 4.28 which is the Samsung software that runs on Windows that will allow us to flash our new boot-loader and ROM over the USB cable that came with the phone. We also need an OPS file which is a text type document that specifies the phones perimeters to ODIN so that it can flash (install) the ROM correctly. Download to your Samsung folder ODINv4.28 and the OPS file EUROPA_v1.0.ops
Step 2 – Let’s Do It!
The following tutorial (edited) taken from MADTEAM with acknowledgement and thanks to MayurV
Copy to your phones micro SD card, ‘update-cm-7.1.0-galaxy5-v1.7.2-MADTEAM-signed’, ‘v1.7.2-hotfix1’ and ‘gapps-gb-20110815-signed’ before proceeding. This is best done by removing it and inserting it into a P.C’s or laptop’s SD card reader, if it has one.
2.1 First we have to get into Samsung standard recovery mode. You can enable this mode by following screenshot shown below. You phone must be turned off with the USB unplugged before doing this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2.2 Now start Odin Multi Downloader v4.28 in your C:\Samsung folder on your PC. You will see following window.
- At first you may notice Odin says ‘Android’ and not ‘GT-I5500’. This is because we have not yet loaded the OPS file.
Your phone must now be in Download Mode and should be connected to the PC with the USB Cable that the phone shipped with. This is the only way Odin can detect your phone.
2.3 Select the OPS file in by clicking the OPS button (No.3) and the ClockworkMod-Galaxy5-v0.5 by clicking the One Package button (No.4).
Once you click on start button you will see all files will write on your phone, it will take around 1-7 minutes.
Once you see “PASS” in ODIN tool, you can remove USB cable from PC. Once your phone has rebooted and you will see following screen shown below.
*Edit** you do not need to wait for the PASS sign anymore. Once you see the handset screen change to the picture below, close Odin with the red ‘X’ window button, disconnect your USB cable and continue.
2.4 If you are new to use ClockworkMod recovery manager then before doing anything, please have a look at next screen to learn the navigation keys.
2.5 First we have to wipe our old DATA which is not compatible with ClockworkMod. Wiping old DATA is necessary if you are installing for the first time.
- Press BACK (H/W) button on phone and follow next screen.
- Press BACK (H/W) button on phone and follow next screen.
- Press BACK (H/W) button on phone and follow next screen.
- Press BACK (H/W) button on phone and follow next screen.
2.5 Now it’s time for the ROM installation.
Important Note:
• You MUST install the three files in this exact order:
• The main ROM package ‘update-cm-7.1.0-galaxy5-v1.7.2-MADTEAM-signed.zip’
• The hotfix package ‘v1.7.2-hotfix1.zip’
• The Google Apps package ‘gapps-gb-20110828-signed.zip’
- Select to ‘Choose file from SD card’ that you have saved earlier.
Both file should be in ZIP format only. Don’t extract, keep it in ZIP format and store it on SD card.
2.6 Once you are done with installation of these files. Press the BACK button until you return to the first screen shown below. Go to the first option and do reboot.
2.7 On next start-up, you will see CyanogenMod 7 Logo and system will load in few mins. Enjoy your new phone software!
We hope you all get successful installations of ClockworkMod 7 ROM’s
Written by Phillip Thorne – A.K.A sparkyuiop
Nice summary, thanks. Can I add a couple of points? Do not use CWM v6, it just times out when flashing with Odin. If you want to flash a new UK baseband you can download the latest one (I5500XWJP4) here http://www.multiupload.com/81IBI2MD0X - the one listed on the baseband page does not work.
Baseband and unlocking?
dwl99 said:
If you want to flash a new UK baseband you can download the latest one ...
Click to expand...
Click to collapse
What does flashing the baseband achieve? I assume this will not unlock the phone?
I would also like to add that once people have loaded this ROM onto their Samsung G5 there are many safe ways to extract the 8 digit passcode number to unlock the phone to any network.
I had previously used Jc_master method to extract the passcode which worked on the first one and second one that I did but for some reason the second one failed to reboot after and became bricked. (This was done prior to flashing a non-samsung ROM on both phones and I believe it will not work on the Cyanogen ROM)
This method looks good but I have not yet tried it: method
sparkyuiop said:
What does flashing the baseband achieve? I assume this will not unlock the phone?
I would also like to add that once people have loaded this ROM onto their Samsung G5 there are many safe ways to extract the 8 digit passcode number to unlock the phone to any network.
I had previously used Jc_master method to extract the passcode which worked on the first one and second one that I did but for some reason the second one failed to reboot after and became bricked. (This was done prior to flashing a non-samsung ROM on both phones and I believe it will not work on the Cyanogen ROM)
This method looks good but I have not yet tried it: method
Click to expand...
Click to collapse
Flashing a new baseband ensures that the GPS & phone will continue to work. Although you might want to do it only if anything doesn't work after you flash the ROM.
It isn't working, it will not detect the ops file despite my downloading it to C:/Samsung. Any advice?
Update:
I removed the .txt from the ops filename, now its working
Rad, clear and concise.
Cheers!
gwildor said:
Rad, clear and concise.
Cheers!
Click to expand...
Click to collapse
Thank You. I'm no expert at this so I'm pretty chuffed it's working out for people.
Tactics119 said:
It isn't working, it will not detect the ops file despite my downloading it to C:/Samsung. Any advice?
Update:
I removed the .txt from the ops filename, now its working
Click to expand...
Click to collapse
The OPS file should not be a text (.txt) extension (as you found out). One way to check it has the correct extension is to do this:
Open 'Computer' or 'My Computer'
At the top of the page click 'Organize' or 'View'
Select 'Folder and search options' or 'View'
Move the radio dot from 'Don't show hidden files, folders and drives' to 'Show hidden files, folders and drives'
Click 'Apply' then 'OK'
Go back to your OPS file and read it
Your OPS should read like this: EUROPA_v1.0.ops
If it reads: EUROPA_v1.0.ops.txt or EUROPA_v1.0.txt edit it so it looks like how it should read.
Clockwork Mod isn't a bootloader, it's a recovery!
Sent from my GT-I5500 using Tapatalk
It would be useful for someone, maybe, to update this good how-to, wouldn't it?
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
brainvision said:
It would be useful for someone, maybe, to update this good how-to, wouldn't it?
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
Click to expand...
Click to collapse
Hey man don't steal me thunder! LOL, that's fine with me!
followed all the instructions and the phone just says android in white writing then goes to the samsung screen and back again?
in a cycle?
anyone help me im desparate!
thanks
edit after a few attempts i use odin to flash again and get into clock work.........
anyone please please !!!1 its my wifes phone and shes going mad!
managed to get it back by flashing I5500XXJED_Android_2.1 with odin............
does this help and why i cant flash cynogen or any other rom?
Gavin01 said:
followed all the instructions and the phone just says android in white writing then goes to the samsung screen and back again?
in a cycle?
anyone help me im desparate!
thanks
edit after a few attempts i use odin to flash again and get into clock work.........
anyone please please !!!1 its my wifes phone and shes going mad!
managed to get it back by flashing I5500XXJED_Android_2.1 with odin............
does this help and why i cant flash cynogen or any other rom?
Click to expand...
Click to collapse
Yes I am getting same screen after following installtion steps here, Please help..
anishmathw said:
Yes I am getting same screen after following installtion steps here, Please help..
Click to expand...
Click to collapse
did you wipe the phone with ClockworkMod?
Is it me or dose the installing of the samsung usb drivers take a long time to install( about 1 hour)...??
---------- Post added at 10:32 PM ---------- Previous post was at 09:47 PM ----------
Thanks for this...worked perfect,I now have ClockworkMod 7 on my Samsung Galaxy 5 (Europa) phone... 5 stars..
anishmathw said:
Yes I am getting same screen after following installtion steps here, Please help..
Click to expand...
Click to collapse
Gavin01 said:
followed all the instructions and the phone just says android in white writing then goes to the samsung screen and back again?
in a cycle?
anyone help me im desparate!
thanks
edit after a few attempts i use odin to flash again and get into clock work.........
anyone please please !!!1 its my wifes phone and shes going mad!
managed to get it back by flashing I5500XXJED_Android_2.1 with odin............
does this help and why i cant flash cynogen or any other rom?
Click to expand...
Click to collapse
brainvision said:
did you wipe the phone with ClockworkMod?
Click to expand...
Click to collapse
i have having the same issues as well... flash CWM with odin, boots fine into CWM, flash CM7 and gapps, and just get the white android writing
i did the following steps:
1. flash CWM with odin
2. in recovery, wiped data, wiped cache, wiped dalvik, wiped battery stats
3. flashed CM7 and gapps
4. just for good measures i wipe cache and dalvik
4. reboot
doing that gets me into boot loop, just keeps giving me the white android writing over and over again.
(off topic here a bit)
tried to go back to stock with odin and still have bootloop with samsung writing on the screen.... so far the phones a brick... cannot get it to boot into any ROM at all
Just let you know that on my phone the camera is not working properly,when recording it shudders and if you switch back to photo mode it crashes.
---------- Post added at 05:43 PM ---------- Previous post was at 05:04 PM ----------
c_86 said:
i have having the same issues as well... flash CWM with odin, boots fine into CWM, flash CM7 and gapps, and just get the white android writing
i did the following steps:
1. flash CWM with odin
2. in recovery, wiped data, wiped cache, wiped dalvik, wiped battery stats
3. flashed CM7 and gapps
4. just for good measures i wipe cache and dalvik
4. reboot
doing that gets me into boot loop, just keeps giving me the white android writing over and over again.
(off topic here a bit)
tried to go back to stock with odin and still have bootloop with samsung writing on the screen.... so far the phones a brick... cannot get it to boot into any ROM at all
Click to expand...
Click to collapse
I have put this rom on my phone twice now and it sounds like you are doing it wrong and missing the file "v1.7.2-hotfix1.zip"..
This is how i did it..
Started odin
This is how mine looks..
Remember to copy update-cm-7.1.0-galaxy5-v1.7.2-MADTEAM-signed.zip,v1.7.2-hotfix1.zip,gapps-gb-20110828-signed.zip to your sd card,If you can't via phone use your card reader on your pc.
But all mine files are in the Samsung folder,so..
OPS - C:\Samsung\EUROPA_I5500_v1.0.ops
One Package - C:\Samsung\ClockworkMod-Galaxy5-v0.5.tar(ClockworkMod recovery manager)
Make sure everything is left ticked when starting odin just make sure one package is ticked..
switch phone off and plug in usb cable in phone(make sure you have installed the usb drivers,once in download mode you will see them installing wait for them to finish installing.)
Download mode - hold vol - down then middle button then off/on button and wait for download mode pic to come up.
you will see COM3 go orange in odin,press start and it will download ClockworkMod recovery manager to your phone and boot it..
Now wipe - data/Factory reset - yes
Now wipe - cache partition - yes
Now wipe - advanced - Dalvik cache - yes - back - Battery Stats - yes
You MUST install the three files in this exact order:
The main ROM package ‘update-cm-7.1.0-galaxy5-v1.7.2-MADTEAM-signed.zip’
The hotfix package ‘v1.7.2-hotfix1.zip’
The Google Apps package ‘gapps-gb-20110828-signed.zip’
all files should be in ZIP format only. Don’t extract, keep it in ZIP format and store it on SD card.
on phone - ClockworkMod recovery manager - install zip from cdcard - choose zip from sdcard - click on each file and install it in order,once you have done that restart your phone and your done..
Well that how I did it and it worked every time..
Good luck..
P.S If anyone wants to show a video on how to do it let me know.
Video here.. http://www.youtube.com/watch?v=dYmTps4tdwU
Looks like I bricked it...help please.
Tried this today and only got as far as attempting to install ClockworkMod. ODIN went to downloading recovery image and then hung there. Over an hour there. So I disconnected...now my phone is ummm...not working. Any ideas?
Benglian said:
Tried this today and only got as far as attempting to install ClockworkMod. ODIN went to downloading recovery image and then hung there. Over an hour there. So I disconnected...now my phone is ummm...not working. Any ideas?
Click to expand...
Click to collapse
It's obvious that it doesn't work anymore for now: I presume it shows up an interrupted link between the phone and PC..
So remove the battery, restart the PC and do it again.. maybe you miss the USB Samsung driver: try to reinstall them.. and use the 0.5 or 0.7 tar file for now
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
brainvision said:
It's obvious that it doesn't work anymore for now: I presume it shows up an interrupted link between the phone and PC..
So remove the battery, restart the PC and do it again.. maybe you miss the USB Samsung driver: try to reinstall them.. and use the 0.5 or 0.7 tar file for now
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
Click to expand...
Click to collapse
Just the 0.7 tar,
Hi All,
After a failed attempt to root my L9 769, I have an issue where when the phone is turned on, it does not boot, it goes to a screen with the LG logo and the words "security error" beneath it. The phone then powers off. The only thing I have access to on the phone is this screen and the software update mode. I used the offline flash method in my root attempt. I am sure I screwed up in the process. I have scoured the internet in an attempt to resolve this, but I have yet been able to. This seems to be a fairly common problem when a root attempt fails, however I cannot correct this.
Things I have tried:
Fastboot: I try to run fastboot, but it stops at waiting for device.
Offline flash: I tried the offline flash method, but the tool freezes at 15% saying the device cannot be found.
Online flash: The tool recognizes the phone but sees it as being up to date. I try to use the recovery option but it locks up at analyzing the phone.
I am at a loss. Any help would be greatly appreciated.
Thanks,
J
jlj012 said:
Hi All,
After a failed attempt to root my L9 769, I have an issue where when the phone is turned on, it does not boot, it goes to a screen with the LG logo and the words "security error" beneath it. The phone then powers off. The only thing I have access to on the phone is this screen and the software update mode. I used the offline flash method in my root attempt. I am sure I screwed up in the process. I have scoured the internet in an attempt to resolve this, but I have yet been able to. This seems to be a fairly common problem when a root attempt fails, however I cannot correct this.
Things I have tried:
Fastboot: I try to run fastboot, but it stops at waiting for device.
Offline flash: I tried the offline flash method, but the tool freezes at 15% saying the device cannot be found.
Online flash: The tool recognizes the phone but sees it as being up to date. I try to use the recovery option but it locks up at analyzing the phone.
I am at a loss. Any help would be greatly appreciated.
Thanks,
J
Click to expand...
Click to collapse
About offline flash I had the same problem that it couldn't connect to my device but when I used another computer it could find it.
jlj012 said:
Hi All,
After a failed attempt to root my L9 769, I have an issue where when the phone is turned on, it does not boot, it goes to a screen with the LG logo and the words "security error" beneath it. The phone then powers off. The only thing I have access to on the phone is this screen and the software update mode. I used the offline flash method in my root attempt. I am sure I screwed up in the process. I have scoured the internet in an attempt to resolve this, but I have yet been able to. This seems to be a fairly common problem when a root attempt fails, however I cannot correct this.
Things I have tried:
Fastboot: I try to run fastboot, but it stops at waiting for device.
Offline flash: I tried the offline flash method, but the tool freezes at 15% saying the device cannot be found.
Online flash: The tool recognizes the phone but sees it as being up to date. I try to use the recovery option but it locks up at analyzing the phone.
I am at a loss. Any help would be greatly appreciated.
Thanks,
J
Click to expand...
Click to collapse
You need a recovery.img from p769 and flash it through fastboot
Download https://mega.co.nz/#!7RxjnDyS!gYY7Zs6naT4fa3Oj1FfIFu2O_sfEtL1awPD-HOSOu_E
Then type in fastboot "fastboot flash recovery p4_769.img"
Sent from my LG-P769 using Tapatalk 4
I have the same issue adb won't connect no fastboot
Sent from my Amazon Kindle Fire using xda app-developers app
You need to flash the ice cream x & u boot for your device (in fastboot) to get the offline flash running again.
Some help on how to install fastboot
Did you install the omap4430 driver twice?
Open an elevated command prompt and type
Code:
SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
devmgmt.msc
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then open the Device Manager and see if you have the omap4 driver installed twice (in two locations)
Note: In Device Manager click the View tab and select Show hidden devices
If you don't see the omap driver installed twice, do this
Select the "other devices" and start deleting/uninstalling all of the devices you find here (I think the device you are looking for is "lg u2" but not 100% sure)
Once you have uninstalled all of the unknown drivers you found, run the start.bat again and follow the directions to flash the x & u img's (for your device).
Now go back to device manager and find the new unknown/other device created (should be lg u2) and install the omap4430 like you did the first time.
After you have done all this, rerun the start.bat and hopefully it will work for you.
Another thing, If you do see the omap driver installed twice, then it has to be your timing when you enter the battery. Keep trying different times to enter the battery
example. wait 1 second and enter battery, if that doesn't work wait 2 seconds then enter battery and etc.
Good luck
No luck yet with connecting to fastboot, I will give this a shot and report back. Thank you.
You were absolutely right, the issue was with having multiple drivers. I followed your steps and restored my phone to life. Thank you so much.
jlj012 said:
No luck yet with connecting to fastboot, I will give this a shot and report back. Thank you.
Click to expand...
Click to collapse
Your are welcome, now hit the thanks button, it makes me feel good, Lol.
CM 10.1 P769
kuma82 said:
Your are welcome, now hit the thanks button, it makes me feel good, Lol.
CM 10.1 P769
Click to expand...
Click to collapse
Lol..
Sent from my LG-P769 using Tapatalk 4
Got fastboot working, but now what?
kuma82 said:
You need to flash the ice cream x & u boot for your device (in fastboot) to get the offline flash running again
Click to expand...
Click to collapse
@kuma82,
Before I start, I had NO IDEA how crazy the L9 was! I've rooted/unlocked/custom recoveried/custom ROMed 4 other phones without any major set backs prior to hitting this wall.
Also, this is my daughter's phone and I'm really took a lot of precautions before starting.
Here is what I did prior to attempting to wipe (factory reset) and install CM 10.1 (here):
Device model: P769
[was] rooted
CWM Recovery [was] installed
Stock JB (T-Mobile US) ROM backed up (full nandroid)
I was concerned about the many submodels of the L9 and verified both in the about phone within the ROM settings as well as what's printed/etched below the battery under the back cover. Both checked out to be P769.
I ran `adb reboot recovery` and then proceeded to wipe/factory rest from within CWM recovery. After this, I installed the ROM zip from the external sdcard. It failed the update script's assert of ro.product.id and would not install. OK, bummer, I'll just restore the nandroid backup. Nope. It was unable to restore /system and so now I really got concerned. I then found the weirdest thing of all. After seeing what is asserted in the update script for the ROM zip, I ran getprop for each of the properties it checks for and got back the Prada 3D "p940"!
Well now I felt like I was in a world of pain, so I decided to hack the update script so that "p940" would be accepted. Well now the install went fine without any errors reported. I proceeded to flash the latest gapps for 4.2.2 and it too installed fine. GREAT! Now for the system boot.........
From that point on, I've been stuck in LG Security Error land
I was able to get the special fastboot to connect (after many failed attempts) by selecting option 5 for ICS x & u flashing.
Could someone be please be kind enough to help me get my daughter's phone back to some ROM? I'm alright with even stock right now. At least then she'll have a functioning phone and I could even extract apps to restore from the CWM nandroid I made via Titanium.
peace.
erraggy said:
@kuma82,
Before I start, I had NO IDEA how crazy the L9 was! I've rooted/unlocked/custom recoveried/custom ROMed 4 other phones without any major set backs prior to hitting this wall.
Also, this is my daughter's phone and I'm really took a lot of precautions before starting.
Here is what I did prior to attempting to wipe (factory reset) and install CM 10.1 (here):
Device model: P769
[was] rooted
CWM Recovery [was] installed
Stock JB (T-Mobile US) ROM backed up (full nandroid)
I was concerned about the many submodels of the L9 and verified both in the about phone within the ROM settings as well as what's printed/etched below the battery under the back cover. Both checked out to be P769.
I ran `adb reboot recovery` and then proceeded to wipe/factory rest from within CWM recovery. After this, I installed the ROM zip from the external sdcard. It failed the update script's assert of ro.product.id and would not install. OK, bummer, I'll just restore the nandroid backup. Nope. It was unable to restore /system and so now I really got concerned. I then found the weirdest thing of all. After seeing what is asserted in the update script for the ROM zip, I ran getprop for each of the properties it checks for and got back the Prada 3D "p940"!
Well now I felt like I was in a world of pain, so I decided to hack the update script so that "p940" would be accepted. Well now the install went fine without any errors reported. I proceeded to flash the latest gapps for 4.2.2 and it too installed fine. GREAT! Now for the system boot.........
From that point on, I've been stuck in LG Security Error land
I was able to get the special fastboot to connect (after many failed attempts) by selecting option 5 for ICS x & u flashing.
Could someone be please be kind enough to help me get my daughter's phone back to some ROM? I'm alright with even stock right now. At least then she'll have a functioning phone and I could even extract apps to restore from the CWM nandroid I made via Titanium.
peace.
Click to expand...
Click to collapse
To install custom rom or CM10 you need to unlock bootloader first. You should follow kuma82 in his post above to flash back stock rom.
The security error is because you didn't unlock it (sorry to hear that). Just flash with fastboot ice x & u for p769. Then put your phone in s/w upgrade and run the offline flash.
If you need anymore help, holla! I don't want your daughter mad at you
kuma82 said:
The security error is because you didn't unlock it (sorry to hear that). Just flash with fastboot ice x & u for p769. Then put your phone in s/w upgrade and run the offline flash.
If you need anymore help, holla! I don't want your daughter mad at you
Click to expand...
Click to collapse
I swear I read every link you posted above and still could not figure out what: "flash with ice x & u" is. I downloaded the fastboot zip and ran start.bat and selected option 5 for ICS x & u for p769 and that got me an inverted LG fastboot screen. I was also able to then choose option 1 for fastboot which dropped me into an empty yours directory.
It was midnight and I had at least 8 browser tabs open to various xda posts, but I still couldn't figure out what I needed to do with the start.bat next.
Thanks in advance. My weekend is dedicated to solely fixing her phone
Sent from my HTC Sensation using Tapatalk 4
jlj012 said:
Hi All,
After a failed attempt to root my L9 769, I have an issue where when the phone is turned on, it does not boot, it goes to a screen with the LG logo and the words "security error" beneath it. The phone then powers off. The only thing I have access to on the phone is this screen and the software update mode. I used the offline flash method in my root attempt. I am sure I screwed up in the process. I have scoured the internet in an attempt to resolve this, but I have yet been able to. This seems to be a fairly common problem when a root attempt fails, however I cannot correct this.
Things I have tried:
Fastboot: I try to run fastboot, but it stops at waiting for device.
Offline flash: I tried the offline flash method, but the tool freezes at 15% saying the device cannot be found.
Online flash: The tool recognizes the phone but sees it as being up to date. I try to use the recovery option but it locks up at analyzing the phone.
I am at a loss. Any help would be greatly appreciated.
Thanks,
J
Click to expand...
Click to collapse
I've been wanting to try this: go to your computer and check your device manager and disable the LG drivers then try the offline flash again. Kuma way works but it's very long, found this while I was reading but never tried for our phones. Same problem though as updating stops at 15 %
Sent from my LG-P769(v20f) using the xda-developers app. Hit the thanks bottom, makes me feel good!
erraggy said:
I swear I read every link you posted above and still could not figure out what: "flash with ice x & u" is. I downloaded the fastboot zip and ran start.bat and selected option 5 for ICS x & u for p769 and that got me an inverted LG fastboot screen. I was also able to then choose option 1 for fastboot which dropped me into an empty yours directory.
It was midnight and I had at least 8 browser tabs open to various xda posts, but I still couldn't figure out what I needed to do with the start.bat next.
Thanks in advance. My weekend is dedicated to solely fixing her phone
Sent from my HTC Sensation using Tapa talk 4
Click to expand...
Click to collapse
More help with fastboot
http://forum.xda-developers.com/showpost.php?p=44578108&postcount=34
http://forum.xda-developers.com/showpost.php?p=44653501&postcount=55
Another thing, more than likely, after you flash with the r&d tool you will need to do a hard reset because you flashed cyanogen. Also, you will still need to root to fix the touch screen.
CM 10.1 P769
Sent from my LG-P769 using xda app-developers app
kuma82 said:
More help with fastboot
http://forum.xda-developers.com/showpost.php?p=44578108&postcount=34
http://forum.xda-developers.com/showpost.php?p=44653501&postcount=55
CM 10.1 P769
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I was able to repeatedly get the inverted LG fastboot screen and see everything you saw in device manager as well as successfully get `fastboot devices` to show (echo) the device. I even tried `fastboot flash recovery p4_769.img` with the file linked in post #3 and it flashed without error.
Here's my problem: What do I need to do now that I have a working way to run fastboot commands? Is there a recovery image I need to flash (stock)? Is there a boot image I need to flash? Or, is there some other fastboot command I need to run?
I'm assuming the advice you're giving me is to ultimately get a stock ROM back on her phone. Is that correct?
I'd really like to unlock the bootloader so that I can do what I know with CWM: backup, wipe, restore, flash, etc... If that is something I can do from where I'm at now, I'd prefer to put the effort in to that. If this darned 'Security Error' splash message must be resolved by getting back to a stock ROM first, then I'm game.
Final request for clarification: Am I still needing to "flash the ice cream x & u boot for your device (in fastboot) to get the offline flash running again"? If so, could you please provide instructions for that step? So far all of the steps linked here have been to get Windows drivers sorted out and fastboot working. I've got that now.
Thanks again!
erraggy said:
Yeah, I was able to repeatedly get the inverted LG fastboot screen and see everything you saw in device manager as well as successfully get `fastboot devices` to show (echo) the device. I even tried `fastboot flash recovery p4_769.img` with the file linked in post #3 and it flashed without error.
Here's my problem: What do I need to do now that I have a working way to run fastboot commands? Is there a recovery image I need to flash (stock)? Is there a boot image I need to flash? Or, is there some other fastboot command I need to run?
I'm assuming the advice you're giving me is to ultimately get a stock ROM back on her phone. Is that correct?
I'd really like to unlock the bootloader so that I can do what I know with CWM: backup, wipe, restore, flash, etc... If that is something I can do from where I'm at now, I'd prefer to put the effort in to that. If this darned 'Security Error' splash message must be resolved by getting back to a stock ROM first, then I'm game.
Final request for clarification: Am I still needing to "flash the ice cream x & u boot for your device (in fastboot) to get the offline flash running again"? If so, could you please provide instructions for that step? So far all of the steps linked here have been to get Windows drivers sorted out and fastboot working. I've got that now.
Thanks again!
Click to expand...
Click to collapse
Okay, did you get all your info about unlocking the bootloader from carloswii5 video? So you had flashed 20b kdz right?
You gave me a hand full Lola, but I'm help you out. It get is going to take me some time to give you a guide, but I'll give you everything you need today and yes, you need to get back to stock.
I'll send you another link on how to use fast boot manually. Plus it has the images for ice cream. But hold up
Sent from my LG-P769 using xda app-developers app
kuma82 said:
Okay, did you get all your info about unlocking the bootloader from carloswii5 video? So you had flashed 20b kdz right?
You gave me a hand full Lola, but I'm help you out. It get is going to take me some time to give you a guide, but I'll give you everything you need today and yes, you need to get back to stock.
I'll send you another link on how to use fast boot manually. Plus it has the images for ice cream. But hold up
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
THANKS!
Her phone had the stock TMOUS jelly bean ROM that we received OTA. I had only rooted her phone previous to my CM10.1 fiasco attempt.
So I've never flashed anything (successfully at least) on her phone. All of my previous android experience has been on 3 nexuses (One, S, 4) and my current HTC Sensation. That means I've only unlocked one bootloader that didn't support the fastboot oem method
I'm an experienced dev with the entire weekend to "play" with my daughter's p769
I also promise to provide lengthy posts in the Optimus L9 forums to help any future people from soft bricking any more devices.
Sent from my HTC Sensation using Tapatalk 4
This will tell you how to use fastboot manually http://forum.xda-developers.com/showpost.php?p=43642515&postcount=21
The system image is to big to flash with fastboot, sucks.
1. Use the above to get back on stock (you need 10g kdz).
To enter s/w upgrade remove battery. Hold volume up and enter USB cable, then put the battery back in.
Sent from my LG-P769 using xda app-developers app
kuma82 said:
This will tell you how to use fastboot manually http://forum.xda-developers.com/showpost.php?p=43642515&postcount=21
The system image is to big to flash with fastboot, sucks.
1. Use the above to get back on stock (you need 10g kdz).
To enter s/w upgrade remove battery. Hold volume up and enter USB cable, then put the battery back in.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
UH OH... The "volume up" method isn't working on this device. I posted more details about it here. I'm beginning to think I may need to return the phone. I never thought flashing a ROM zip in CWM recovery could brick the phone. When I restoring the CWM backup also failed (when I at least was in CWM recovery which now is inaccessible), I freaked.
P.S. - I'm all out of thanks for the day. I think you got the lion's share though
Anyone have a pair of these glasses and working on root access? Anyone interested? There are a group of us that would be really interested in finding a solution.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dvegaman said:
Anyone have a pair of these glasses and working on root access? Anyone interested? There are a group of us that would be really interested in finding a solution.
Click to expand...
Click to collapse
I have a pair of the FPV Drone Edition. Have side loaded a few apps. Haven't rooted since Galaxy S3 ( back on iPhone now) am interested to get this going
Hi !
It seems the rooting of intel devices follow the scheme:
-get bootimg
-patch it
-allow oem bootloader (voiding warranty and endangering future updates)
-flash the patched bootimg and pray
Is this correct or did i oversimplify or generalize too much or am i plain wrong, anyone ?
Greetings,
Ender
P.S. Greetings dvegaman
Bump.
Well, BUMP, goddamn
Just came across 2 pairs of these (BT-300s).
If the lack of interest in rooting is due to lack of hardware, reach out to me privately here on XDA; would happily donate one to kickstart some development efforts.
-jd
jdiegmueller said:
Just came across 2 pairs of these (BT-300s).
If the lack of interest in rooting is due to lack of hardware, reach out to me privately here on XDA; would happily donate one to kickstart some development efforts.
-jd
Click to expand...
Click to collapse
Bumping this one up. Have a new pair and looking to root to wake them up some.
Sent from my Moto Z (2) using Tapatalk
This may seem easy to others but I figured out how to do a factory data reset using ADB... something that would've helped when my BT-300 went into a boot loop last weekend...
***DO AT YOUR OWN RISK! NOT RESPONSIBLE FOR BRICKING, ETC..... (but it worked fine for me).
1. Install "minimal_adb_fastboot_v1.4.2_setup.exe" (google it and grab at your own risk) on your Windows PC.
2. Go to the BT-300 and:
a. Under Security allow unknown sources
b. Under Developer Options allow USB debugging and unlock bootloader.
3. Connect same powered up BT-300 to PC via USB cable.
4. Start up that minimal ADB program. It will open in command prompt.
5. Check connection by typing "adb devices"
Should see "EMBT3C device" on PC
6. Now type, "adb reboot recovery" and wait for android with triangle/exclamation point to appear after device reboots. You will notice the physical buttons flash purple too.
7. Press and hold power button. Also press Vol Up, then release Vol Up and finally release Power button.
You should now see the recovery menu including "wipe data/factory reset", cache clear, and so on...
NOW... if I could get recovery.zip image to restore if I "kill" it to reload with ADB... THEN I'd try root. There must be a way. I just want GApps 5.1.1 on the thing for starters.
Still struggling with rooting... No dice so far. I've never rooted any Android... Once rooted can we then save the original factory ROM someplace safe, or do I need that first from another source? Newbie questions . I know just enough to be dangerous! LOL.
I got the factory image
Played around with the "SoftwareUpdate" apk and found the strings it uses to download the 1.4
Ugh just signed up but because I don't have enough posts I had to put a bunch of spaces in the links for them to
show up. Just remove the spaces and they should work? Either his or copy the SoftwareUpdate.apk and pull the strings from that.
ht tps:// download.ebz.epson.net /dsc /du /04 /SecureUpdateInfo ?PRN=BT-300&CTI=80&OSC=ARD&SCD=H756EMBT3C&SID=012345
You download a file called "SecureUpdateInfo" open it in a text editor and it will give you a link to the direct download for the zip. Its about 300megs. I have been playing with the boot options, but keep crashing it on boot and having to restore. I found 4 test pins that may be a serial port, but its 1.8 volt so I need to build something
PS - It might com back without a link but "BUSY" on it. I have been testing it a bunch so thats what happened right now. The fille will look like below
Code:
; secure update information
[BT-300;]
Version=R1.4.0
Size=371659424
Location= ht tps:// download.ebz.epson.net/ dsc/check/ 01/ GetFile. php ?PATH=xxxxxxx/OTA-R1.4.0.zip&KEY=lt1fs0DK
DownloadNumber=11474485
LALocation1=h ttp:// download.ebz.epso n.net/ dsc /hmd_license /EULA.zip
Erodros said:
Played around with the "SoftwareUpdate" apk and found the strings it uses to download the 1.4
Ugh just signed up but because I don't have enough posts I had to put a bunch of spaces in the links for them to
show up. Just remove the spaces and they should work? Either his or copy the SoftwareUpdate.apk and pull the strings from that.
ht tps:// download.ebz.epson.net /dsc /du /04 /SecureUpdateInfo ?PRN=BT-300&CTI=80&OSC=ARD&SCD=H756EMBT3C&SID=012345
You download a file called "SecureUpdateInfo" open it in a text editor and it will give you a link to the direct download for the zip. Its about 300megs. I have been playing with the boot options, but keep crashing it on boot and having to restore. I found 4 test pins that may be a serial port, but its 1.8 volt so I need to build something
PS - It might com back without a link but "BUSY" on it. I have been testing it a bunch so thats what happened right now. The fille will look like below
Code:
; secure update information
[BT-300;]
Version=R1.4.0
Size=371659424
Location= ht tps:// download.ebz.epson.net/ dsc/check/ 01/ GetFile. php ?PATH=xxxxxxx/OTA-R1.4.0.zip&KEY=lt1fs0DK
DownloadNumber=11474485
LALocation1=h ttp:// download.ebz.epso n.net/ dsc /hmd_license /EULA.zip
Click to expand...
Click to collapse
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
chuck1026 said:
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
Click to expand...
Click to collapse
Is the link in the in the secureupdate? I don't know if the strings encode the serial number in some why or if epson is reading this thread
I can pm you a link for the file if you can't get it
Erodros said:
Is the link in the in the secureupdate? I don't know if the strings encode the serial number in some why or if epson is reading this thread
I can pm you a link for the file if you can't get it
Click to expand...
Click to collapse
Yes, pm me the link. Thanks
Sent from my Moto Z (2) using Tapatalk
chuck1026 said:
Yes, pm me the link. Thanks
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
Ok sending now.
I also managed to root my epson! I discovered the twrp.img here:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
If you get into bootloader mode and fastboot flash it into the recovery partition, you can adb root it and then install supersu from there. I just trashed my device though so be sure to do a full image backup first haha.
Erodros said:
Ok sending now.
I also managed to root my epson! I discovered the twrp.img here:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
If you get into bootloader mode and fastboot flash it into the recovery partition, you can adb root it and then install supersu from there. I just trashed my device though so be sure to do a full image backup first haha.
Click to expand...
Click to collapse
You trashed it? What did ya load after root to crash it?
chuck1026 said:
You trashed it? What did ya load after root to crash it?
Click to expand...
Click to collapse
Tried to load up opengapps, then every time I rebooted it would be "optimizing apps" I tried to side-load the OTA again and poof, it killed the system partition.
The ota apparently doesn't have the full image. Right now I am trying to hack together something from another cherry rom and side load it, but I need a DD of someones system Glad twrp still works or I wouldn't have shell root access to fix.
Erodros said:
Tried to load up opengapps, then every time I rebooted it would be "optimizing apps" I tried to side-load the OTA again and poof, it killed the system partition.
The ota apparently doesn't have the full image. Right now I am trying to hack together something from another cherry rom and side load it, but I need a DD of someones system Glad twrp still works or I wouldn't have shell root access to fix.
Click to expand...
Click to collapse
You tell me how to share a pure factory image of mine (I'll gladly do an FDR for the cause)... and I'll share with ya!
chuck1026 said:
You tell me how to share a pure factory image of mine (I'll gladly do an FDR for the cause)... and I'll share with ya!
Click to expand...
Click to collapse
Ok I am retarded. I didn't configure twp correctly so all the folders it had were wrong. So when I went to use the install tool it screwed up majorly.
Just glad I didn't overwrite the bootloader
PS - Ok, I figured out how to restore the original recovery loader and it recovered fine. It must be something in this hacked version of twip that isn't applying the ota correctly. Going to try to build a version of twip just for this
Erodros said:
Ok I am retarded. I didn't configure twp correctly so all the folders it had were wrong. So when I went to use the install tool it screwed up majorly.
Just glad I didn't overwrite the bootloader
Click to expand...
Click to collapse
You are not. I am the noob trying to figure out the whole root process and I don't even know how to backup the existing bootloader and ROM so I can restore it with ADB if I screw it all up in root..... I feel clueless and know just enough to be dangerous... yet for some reason, I'm not afraid, just need to learn.
chuck1026 said:
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
Click to expand...
Click to collapse
Whew! I did it. First I took the instructions from here as a start:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
In fact, if you can "almost" follow the instructions verbatim. The problem is that the data drive is encrypted and the default android password didn't work so I had to modify the boot.img to not encrypt the data partition then do a wipe. supersu installed fine then.
As for gapps, that was tricky. You have to manually install google webview apk as the built in one is garbage.
Still working on the vr settings. Camera has issues with scaling as I think good believes it to be a widescreen when its a 4.3.
Once I get it down, I will make a boot.img and recovery.img that should just work.