Related
Using a viewsonic G Tablet, I had initially loaded the clockwork mod. was working fine. Flashed a few ROMs over the last week. Currently running Cyanogen Mod7 Accidentally wanted to see what the ROM Manager app was about. Went and flashed the Clockword mod. Since then, I'm not able to go back into Clockwork mod. Everytime I try to reboot using the Power and Vol + button, it boots back into CyanogenMod ROM. Has a message related to MRC Erase after it says it detected REcovery Key pressed. I want to go back to using Clockworkmod so that I can flash another ROM. Now my computer doesn't even recognize the g tablet as an external storage so can't even access root. What do I need to do to get back my Clockworkmod to work again and how do I get back to my computer to recognize the g tablet. Appreciate the help. All feedback is welcome.
Sounds like you've reverted to stock recovery. Reinstall ClockworkMod. First part of this thread: http://forum.xda-developers.com/showthread.php?t=865245
Before you do, you might want to check the developers thread for your ROM to make sure there aren't any caveats.
K J Rad said:
Sounds like you've reverted to stock recovery. Reinstall ClockworkMod. First part of this thread: http://forum.xda-developers.com/showthread.php?t=865245
Before you do, you might want to check the developers thread for your ROM to make sure there aren't any caveats.
Click to expand...
Click to collapse
But to install Clockworkmod, I need my computer to recognize the g tab as a external storage device. Something it's not doing. So can't go back to it. CAn I download the clockworkmod on the external SD Card on the computer, put it back in the gtab and let it self recognize it and install clockworkmod? Will that work? And why isn't my computer recognizing my gtab as an external storage device. Is there a way I can mount USB storage without going into clockworkmod?
Have you tried using Rom Manager to flash clockworkmod again? Or used it to flash and older version of Clockworkmod?
If you read the thread it shows there is a method to load CWM from MicroSD card (external). Once you have CWM back on then you can mount internal through it.
I dont know why Your tablet isn't mounting. Mine mounts automatically but my configuration is very different from yours. Perhaps you could check the ROM developers thread for more information.
Double submission. Please ignore/delete.
tcrews said:
Have you tried using Rom Manager to flash clockworkmod again? Or used it to flash and older version of Clockworkmod?
Click to expand...
Click to collapse
I used the ROM Manger to flash clockworkmod. That's what messed up the clockworkmod in the first place. Trying to see how to fix that. May need to get rid of the ROM Manager.
Flash the alternate recovery in Rom Manager and then delete Rom Manager
thebadfrog said:
Flash the alternate recovery in Rom Manager and then delete Rom Manager
Click to expand...
Click to collapse
I can't even flash clockwork mod from the ROM manager. Keeps giving me a message "An Error occured while attempting to run privileged commands". Using clockworkmod was just so much easier. Just touching one button the ROM Manager has caused me headaches. I need some serious help.
Then run nvflash from the development froum
thebadfrog said:
Then run nvflash from the development froum
Click to expand...
Click to collapse
Tried to run NVFlash, but I get through ok till the point where I have to run the .bat script. What am I doing wrong? Where do I run it? Do I just double click? Because it reports an error when I do that. I"m using Windows 7 64 bit on a HP touchsmart. able to download the usb driver. recognizes the APX. but can't run the last command. Am I just supposed to get a black screen when I boot using Power and vol - button? Cos nothing else shows up on it. Appreciate the help.
I am also Unable to get into CWM after doing an update in Rom Manager. Have tried a bunch of things. still no luck. Power>Reboot>Recovery and RomManager just get me the Deterct Recovery Command - Erasing MCS then straight into CM7
Power/+ gets me Recovery Key Detected but then boots right into CM7.
Please let me know how you make out.
Childpsy said:
Tried to run NVFlash, but I get through ok till the point where I have to run the .bat script. What am I doing wrong? Where do I run it? Do I just double click? Because it reports an error when I do that. I"m using Windows 7 64 bit on a HP touchsmart. able to download the usb driver. recognizes the APX. but can't run the last command. Am I just supposed to get a black screen when I boot using Power and vol - button? Cos nothing else shows up on it. Appreciate the help.
Click to expand...
Click to collapse
When the tablet is put into APX mode the screen will go black. I don't use windows so I can't be much help with the rest but it would help if you told us what the error is when you try to start the file.
Thunter75 said:
I am also Unable to get into CWM after doing an update in Rom Manager. Have tried a bunch of things. still no luck. Power>Reboot>Recovery and RomManager just get me the Deterct Recovery Command - Erasing MCS then straight into CM7
Power/+ gets me Recovery Key Detected but then boots right into CM7.
Please let me know how you make out.
Click to expand...
Click to collapse
That's exactly what is happening. Was wanting to load the TNT lite or Vegan to try out a different rom and now I can't do it.
K J Rad said:
When the tablet is put into APX mode the screen will go black. I don't use windows so I can't be much help with the rest but it would help if you told us what the error is when you try to start the file.
Click to expand...
Click to collapse
I will post the error message once I try it again at home. I do get the black screen. Thanks for your help.
Error message when trying NVFlash
K J Rad said:
When the tablet is put into APX mode the screen will go black. I don't use windows so I can't be much help with the rest but it would help if you told us what the error is when you try to start the file.
Click to expand...
Click to collapse
The Message that shows up on the command window
"nvflash.exe" ---bct gtablet.bct ---setbct ---bl bootloader.bin ---configfile gtablet.cfg --create --go
NVFlash Started
NVFlash configuration file error: file not found
Please enter to continue
That's exactly what I see when I double click the nvflash_gtablet Windows batch file
Alright so I tried a few things and it seems like I needed to copy the files rather than the folder to the NVFlash folder. So I did that. NVFlash was successful but now it's stuck in boot loop. Now what do I do?
Ok... if you read any amount of the flashing process threads you would know using rom manager is a quote"****ing bad idea"end quote. Nvflash and a repartition using cwm is your only hope.
Flash cwm as an update.zip and repartition
err k. so im a complete idiot. some how i managed not only to format my system but then also delete every file on the sd card. so i cant boot into recovery cus it dont exist any more. and for some reason i can also no longer flash rom.tar files or cwm.tar file using odin. have any idea what i should do or am i just screwed?
buffsterboy15 said:
err k. so im a complete idiot. some how i managed not only to format my system but then also delete every file on the sd card. so i cant boot into recovery cus it dont exist any more. and for some reason i can also no longer flash rom.tar files or cwm.tar file using odin. have any idea what i should do or am i just screwed?
Click to expand...
Click to collapse
I would first try to get into download mode. If you can get into download mode, then you can flash the build. If you can't get into download mode, then you might be screwed. Jump over to the irc channel in my signature and tell them which phone it is and see if they can help you out. I should be back in there soon if no one is available.
i do have a limited android recovery that would let me apply sdcard update.zip
buffsterboy15 said:
i do have a limited android recovery that would let me apply sdcard update.zip
Click to expand...
Click to collapse
That's the stock recovery - if you are able to get into that then you most likely should be able to get into download mode (which would enable you to flash the stock build in odin.) Like phidelt82 said, jump in the IRC chat when you can - we're always there to help. Otherwise I suggest you go back to the stock thread and read those instructions carefully and try again.
I had this happen too once.
Just take the battery out, hold your volume down button and donwload mode should show up.
Get a copy of oden / froyo 2.2 and you'll be up and running in minutes.
I was using this guide http://forum.xda-developers.com/showthread.php?t=1078019 to unlock, install CWM, and then root. Unlocking was fine, installing that version of CWM seemed okay, but when I enter command "fastboot reboot", then hold down the volume - button after 3 seconds of the Moto logo showing, then pressing the volume + key, I get only 1 option....-->Android Recovery. I press the Volume + key, get "Entering Android Recovery Mode", and below that "Reading ODM Fuse 1", then the screen switches to an android with a yellow hazard sign in his tummy.
From that screen, if I press Volume + and power, I see:
Android system recovery <3e>
Use volume keys to highlight; power button to select.
reboot system now
apply update from USB drive
wipe data/factory reset
wipe cache partition
I don't get a choice to apply something from the microSD card I have installed with the WiFi_RootTool_3.1.zip I put on the card.
Has anyone had this happen? I can't ask in the development forum. I also just got the Xoom back from a repair, and it was wiped to stock, then I did the 3.1 update when I got it back this morning. Is the fuse thing something they may have done to block rooting?
Have you tried reformat your sd card?
becu4xda said:
Have you tried reformat your sd card?
Click to expand...
Click to collapse
I'll try that. But would that stop it from going into recovery?
becu4xda said:
Have you tried reformat your sd card?
Click to expand...
Click to collapse
I reformatted my sd card, but I still can't get CWM to work and boot into recovery. Same message-
-->Android Recovery
Entering Android Recovery Mode
Reading ODM fuse: 1
And that's it....no options to load the root zip from an SD card or anything. Is there a way to push root without using the SD card? Or is that ODM fuse thing making it impossible?
becu4xda said:
Have you tried reformat your sd card?
Click to expand...
Click to collapse
Nothing at all to do with CWM.
OP: Try flashing the recovery again. To get into recovery, type adb reboot recovery, or use an app such as Quick Boot.
Edit: You can't use CWM to root, you need to do that first.
siscim23 said:
Nothing at all to do with CWM.
OP: Try flashing the recovery again. To get into recovery, type adb reboot recovery, or use an app such as Quick Boot.
Edit: You can't use CWM to root, you need to do that first.
Click to expand...
Click to collapse
I have to root first? I'm not sure how to do it....can't find any other methods of rooting 3.1....everything on Google just points me to the same method, using the SD card that won't work cuz I can't boot into recovery. Ugh.
Hey jump hour PM me.
Hey guys,
I called JumpHour and we tried to troubleshoot this over the phone. We aren't able to get into the recovery because of error "reading odm fuse: 1". The OP is using Windows 7 64 BIT and has the SDK installed properly. He updated the sources and installed them so those are up to date. We also verified that USB debugging was enabled and that the correct files were in the tools section in the SDK folder.
We ran the commands:
adb reboot bootloader
fastboot-recovery ........ (we typed it in correctly accoriding the thread)
fastboot reboot
and we get that error message.
This was all initiated while the Xoom was powered on. JumpHour stated that he had to send his Xoom back to Moto because his Xoom got messed up during the re-locking process when he unrooted a one click root and re-locked.
We then went ahead and downloaded the recovery image again and replace the one in the tools folder. We ran the commands again and we were getting the same error.
Does anyone have any idea what is going on with this process? Are we missing something? Is something broken?
Get the official images. I am assuming you have a USA 3g or wifi model.
Follow the steps to return the device to stock. But do not issue the reclock bootloader command. There is no need to relock.
From there power up the device and turn on USB debugging.
Then adb reboot into recovery. That should bring you to the stock recovery.
If all goes well from here just do what ever else you where intending to do in the first place.
You most likely can just flash the stock recovery but I would just do a full flash back to official images minus relocking bootloader.
Sent from my Xoom using Tapatalk
Then let the ota update it to 3.1 and so on.
Sent from my Xoom using Tapatalk
What's the status JumpHour? Did you get it to work. I told you it may have been due to the images. Hopefully that fixes your issue. Take care dude.
gqstatus0685 said:
What's the status JumpHour? Did you get it to work. I told you it may have been due to the images. Hopefully that fixes your issue. Take care dude.
Click to expand...
Click to collapse
Hi, thanks for the response. I'm gonna try it now. I was up REALLY late last night, and just got up a little while ago. I'll definately respond after I try it out.
Finally, I did it!
Okay, I fixed it finally. Reloaded the stock images, and it's now rooted with SD support. Yay! Only took 2 days!
Thanks for all your help guys.
Can reflashing with original images fix recovery mode mount problem?
Does any window is flashing to the original images can restore access to the sdcard IF the recovery mode in the official recovery mode (not CWM) says that you cannot mount the sdcard?
I pulled a boneheaded move and ended up formatting my phone from within the TWRP menu. Now the stock operating system is gone.
I wanted to put on one of the Gummy Nightly builds, but I'm new to TWRP and selected the wrong options while wiping.
So now I have the Gummy ROM on my PC, the phone is connected to my PC and in TWRP (in the advanced adb sideload feature), but adb will not recognize my phone.
When I check device manager, SAMSUNG_Android_SCH-I535 is there, but with a yellow "cauton" symbol. When I look at properties, it tells me that "The drivers for this device are not installed (Code 28).
I went out to the Samsung page and got the exe to unpack drivers on my machine... I've tried "update driver" and pointing to the root of the directory containing the Samsung drivers, but my PC claims none of them are applicable.
So what I'm looking for here is:
(1) How do I get this ROM on my phone so that I can install the zip and have a working OS again?
(2) Assuming that using the ADB Sideload feature of TWRP is my best option, how do I get the device drivers for my galaxy s3 installed to my windows 8 PC and get adb to detect it?
Thanks in advance.
Ok, so it seems to have gotten worse.
I cannot get my windows installation to recognize the phone without it being able to boot an android OS, it seems.
I had it in TWRP 2.6.0.0, but as I was trying to reboot to see if I could get into download mode (my thought being to change out TWRP for Clockwork; I seem to remember Clockwork Recovery having a "mount as USB" option which TWRP seems to lack), it tried to root the file system.
After that, the screen went black and nothing happened... the phone was unresponsive. I would remove the battery and replace it to have it vibrate once and then not respond to any key presses.
I removed the battery, SD card, and SIM card, replacing only the battery and got it to turn on and show a Samsung Galaxy SIII logo... but it's just sitting there... I'm assuming it's frozen because there's no OS to boot on the internal storage.
Please help me recover my phone!
Ok, so I've found I can still get into download mode, but not into recovery.
Recovery seems to lead to a black screen with nothing on it.
Trying to boot normally leads to the statis Samsung Galaxy SIII logo.
Can I fix my phone from the download menu?
Please help me.
Install kies and at the end of the install make sure you check install unified drivers. Then flash root66 through Odin. After that you should be good to install ROMs again.
ThePagel said:
Install kies and at the end of the install make sure you check install unified drivers. Then flash root66 through Odin. After that you should be good to install ROMs again.
Click to expand...
Click to collapse
Thanks for the reply!
Sorry, I'm a little out of date on the flashing and stuff -- I was just over in the thread where the poster thought he half softbricked his phone and was asking about 4.1.2 vs. 4.3
I see this at the top of my screen sitting here in download mode:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: YES (6 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
It seems my bootloader got relocked somehow -- is this why my phone just goes to black screen when I attempt to boot into recovery -- even if I have TWRP or CWR installed? Odin claims I just pushed philz custom CWR to my PDA section, but it still won't go into recovery.
What are my options here?
You are pre 4.3 I'll help you more in the morning if no one else does first.
ThePagel said:
You are pre 4.3 I'll help you more in the morning if no one else does first.
Click to expand...
Click to collapse
Ok, thanks -- I appreciate that someone's willing to help! Googling stuff is just getting me more and more confused.
I'll stay tuned for help and turn off my phone so I don't screw things up further in the meantime.
My desired result here, I think is to have my bootloader remain unlocked (as I was under the impression it was, since I was running TWRP with rooted stock ROM), with CWR as the custom recovery software and Gummy as my current ROM.
Side note: I've noticed I don't even get a battery indicator on the main screen now when I press the home button -- is this because of whatever's causing my recovery to not work (and the potential lack of an OS)?
Thanks in advance.
corrosivefrost said:
Ok, thanks -- I appreciate that someone's willing to help! Googling stuff is just getting me more and more confused.
I'll stay tuned for help and turn off my phone so I don't screw things up further in the meantime.
My desired result here, I think is to have my bootloader remain unlocked (as I was under the impression it was, since I was running TWRP with rooted stock ROM), with CWR as the custom recovery software and Gummy as my current ROM.
Side note: I've noticed I don't even get a battery indicator on the main screen now when I press the home button -- is this because of whatever's causing my recovery to not work (and the potential lack of an OS)?
Thanks in advance.
Click to expand...
Click to collapse
Once you in download mode, can your Odin see your phone?
buhohitr said:
Once you in download mode, can your Odin see your phone?
Click to expand...
Click to collapse
I believe it can. After TWRP stopped working, I tried to replace it with CWR and the digital flash count went up (Odin showed no errors on the flash) -- recovery still won't work though, holding vol+/home/power simply gives me a black screen after I see the SAMSUNG logo with the recovery boot text in the upper left.
corrosivefrost said:
I believe it can. After TWRP stopped working, I tried to replace it with CWR and the digital flash count went up (Odin showed no errors on the flash) -- recovery still won't work though, holding vol+/home/power simply gives me a black screen after I see the SAMSUNG logo with the recovery boot text in the upper left.
Click to expand...
Click to collapse
What stock version do you have on your phone right now?
buhohitr said:
What stock version do you have on your phone right now?
Click to expand...
Click to collapse
None? :silly:
I think before this fiasco, it was running whatever version was previous to the new VZW update.
It was the fact that the new update was trying to install and failing repeatedly (because my bootloader was unlocked, I think?) that prompted me to look into finally switching to a ROM. However, my unfamiliarity with TWRP led to me formatting my phone (everything, it seems, including the SD card)... so I'm not really sure what' "on the phone right now". :\
I'm really not sure what kind of state anything is in at this point -- other than Odin seemingly working and being able to get into download mode.
Again, short version of what happened:
(1) Accidentally did a full wipe (factory reset?) in TWRP -- this wiped the ROM I was going to install with TWRP off the phone.
(2) While trying to ADB sideload from TWRP and telling TWRP to reboot, TWRP tried to install supersu.
(3) After (2), I was unable to get back into recovery mode. I got into Odin and tried to flash philz customer clockwork recovery and it seemed successful. Reboot and attempt to enter recovery still fails. Samsung logo with recovery mode text appears, but then the screen goes black.
(4) Normal boot leaves the screen stuck on the Samsung Galaxy SIII logo indefinitely.
corrosivefrost said:
None? :silly:
I think before this fiasco, it was running whatever version was previous to the new VZW update.
It was the fact that the new update was trying to install and failing repeatedly (because my bootloader was unlocked, I think?) that prompted me to look into finally switching to a ROM. However, my unfamiliarity with TWRP led to me formatting my phone (everything, it seems, including the SD card)... so I'm not really sure what' "on the phone right now". :\
Click to expand...
Click to collapse
OK, download this image and flash with Odin(you should be using Odin version 3.07) http://goo.im/devs/invisiblek/i535/stock.vzw_root66.tar This should bring your phone back from the dead.
Edit: after you have your phone up and running, download goo manager and install cwm recovery since your phone is pre rooted already.
buhohitr said:
OK, download this image and flash with Odin(you should be using Odin version 3.07) http://goo.im/devs/invisiblek/i535/stock.vzw_root66.tar This should bring your phone back from the dead.
Edit: after you have your phone up and running, download goo manager and install cwm recovery since your phone is pre rooted already.
Click to expand...
Click to collapse
Ok, that looks like some version of the stock vzw ROM with root already installed?
This is what ThePagel seemed to recommend as well before I ended up with more questions about what was going on before I did it.
What part of Odin do I flash to? PDA again, just like a custom recovery?
corrosivefrost said:
Ok, that looks like some version of the stock vzw ROM with root already installed?
This is what ThePagel seemed to recommend as well before I ended up with more questions about what was going on before I did it.
What part of Odin do I flash to? PDA again, just like a custom recovery?
Click to expand...
Click to collapse
Yes, it's pre rooted stock image and yes flash with PDA.
buhohitr said:
Yes, it's pre rooted stock image and yes flash with PDA.
Click to expand...
Click to collapse
Standard auto-reboot and f_reset_time options? nothing else necessary?
corrosivefrost said:
Standard auto-reboot and f_reset_time options? nothing else necessary?
Click to expand...
Click to collapse
Correct. When you click on PDA and select the image, give it time to showup in Odin cause the size is big.
buhohitr said:
Correct. When you click on PDA and select the image, give it time to showup in Odin cause the size is big.
Click to expand...
Click to collapse
Alright, I'll give it a shot and report back.
Thank you!
corrosivefrost said:
Alright, I'll give it a shot and report back.
Thank you!
Click to expand...
Click to collapse
If that doesn't work you'll need to flash the bootchain first. I don't have a link but I could find it if you need to use it.
ThePagel said:
If that doesn't work you'll need to flash the bootchain first. I don't have a link but I could find it if you need to use it.
Click to expand...
Click to collapse
Yes if the bootloader is still locked he needs boot chain can be found here http://forum.xda-developers.com/showthread.php?t=2046439
ThePagel said:
If that doesn't work you'll need to flash the bootchain first. I don't have a link but I could find it if you need to use it.
Click to expand...
Click to collapse
It did work! Hooray!
buhohitr said:
Yes if the bootloader is still locked he needs boot chain can be found here http://forum.xda-developers.com/showthread.php?t=2046439
Click to expand...
Click to collapse
Didn't need to go that far -- but now that I'm back up and running, signed into google play, and downloaded goo manager, can you point me in the right direction for getting it to install cwm recovery?
Thanks guys!
Hi everyone,
Forgive me if this is a noob question but I've been searching all night and I cannot find a solution.
Background - A friends sister recently passed away and she asked me if I could somehow get the data off of her phone. The phone is a Boost Mobile LG855 (Marquee). It is not rooted, is not in debug mode and is keylocked. We don't have the unlock code so based on what I've read, my only hope is to get CWM somehow flashed on the phone and use it to back up the phone data to the SD card.
Because I cannot get the phone into debug mode and there doesn't seem to be a download mode on this phone, any of the USB-based flashing techniques will not work. I am able to connect the phone as a storage device and access the SD card from my computer but I can't get the computer to recognize it as an ADB device. So that rules out the fastboot, adb or odin-like methods. I believe my only hope is to use the stock recovery to flash CWM from the SD Card (update.zip method).
I downloaded the CWM image for this phone (recovery-clockwork-5.0.2.8-marquee.img) but I can only flash a file called "update.zip" from the stock recovery options. I read somewhere that I should be able to rename the image file to "recovery.img" and put it in an uncompressed "update.zip" file which I did. I copied it to the SD card and tried the flash it only to get the dreaded "E: signature verification failed" "installation aborted." message.
Here are my questions:
Is what I am trying to do even possible?
Can I flash a .img image by sticking it in an update.zip file?
Do I need to create a /dev/recovery/ structure inside the zip file?
If so, how do I fix the zip file so it doesn't fail the signature verification?
Is there a better way to do what I am trying to do?
There are all kinds of tutorials on how to use CWM to flash things from the SD card but surprisingly few that describe how to do what I am trying.
Any help or suggestions would be most appreciated. Thank you so much in advance.
JZ_Hack_Nub said:
Hi everyone,
Forgive me if this is a noob question but I've been searching all night and I cannot find a solution.
Background - A friends sister recently passed away and she asked me if I could somehow get the data off of her phone. The phone is a Boost Mobile LG855 (Marquee). It is not rooted, is not in debug mode and is keylocked. We don't have the unlock code so based on what I've read, my only hope is to get CWM somehow flashed on the phone and use it to back up the phone data to the SD card.
Because I cannot get the phone into debug mode and there doesn't seem to be a download mode on this phone, any of the USB-based flashing techniques will not work. I am able to connect the phone as a storage device and access the SD card from my computer but I can't get the computer to recognize it as an ADB device. So that rules out the fastboot, adb or odin-like methods. I believe my only hope is to use the stock recovery to flash CWM from the SD Card (update.zip method).
I downloaded the CWM image for this phone (recovery-clockwork-5.0.2.8-marquee.img) but I can only flash a file called "update.zip" from the stock recovery options. I read somewhere that I should be able to rename the image file to "recovery.img" and put it in an uncompressed "update.zip" file which I did. I copied it to the SD card and tried the flash it only to get the dreaded "E: signature verification failed" "installation aborted." message.
Here are my questions:
Is what I am trying to do even possible?
Can I flash a .img image by sticking it in an update.zip file?
Do I need to create a /dev/recovery/ structure inside the zip file?
If so, how do I fix the zip file so it doesn't fail the signature verification?
Is there a better way to do what I am trying to do?
There are all kinds of tutorials on how to use CWM to flash things from the SD card but surprisingly few that describe how to do what I am trying.
Any help or suggestions would be most appreciated. Thank you so much in advance.
Click to expand...
Click to collapse
None of this is necessary..
You can not flash a zip made by us from stock Recovery.
Your final hope is fastboot mode.
Before that, Install Minimal ADB and Fastboot in PC (Google it)
Switch off the mobile.
Hold any button combination like Power + Volume Up (or whatever, it's specific to phone) which will take you to a boot menu.
Connect phone to PC.
Select fastboot option in that menu from phone.
Now open Minimal ADB and Fastboot desktop icon and type the following:
Code:
fastboot boot recovery location_of_recovery\recovery.img
This will boot the CWM recovery.
Do whatever you want there
Thanks for your suggestion. I did start to go down that road and installed fastboot/adb. I gave up when the only key combination I could find for this stupid phone was power+volume down to boot into recovery. I will search more on whether there is a boot menu available on Boost Mobiles crappy stock ROM. Will update on what I find.
Thx again for the suggestion.
JZ_Hack_Nub said:
Thanks for your suggestion. I did start to go down that road and installed fastboot/adb. I gave up when the only key combination I could find for this stupid phone was power+volume down to boot into recovery. I will search more on whether there is a boot menu available on Boost Mobiles crappy stock ROM. Will update on what I find.
Thx again for the suggestion.
Click to expand...
Click to collapse
Inside the recovery, check if you have an option like 'bootloader' or 'fastboot' or 'debug'
If there's something like that, that's the fastboot mode.
Some phones don't have fastboot mode, so the phone might be one of those if there's nothing like that
Anyway, what data do you want to recover from the phone??
Believe it or not, I'm reading that these LG phones require a special cable from shady overseas websites to access the boot loader and flash capabilities.
Awesome...
GokulNC said:
Inside the recovery, check if you have an option like 'bootloader' or 'fastboot' or 'debug'
If there's something like that, that's the fastboot mode.
Some phones don't have fastboot mode, so the phone might be one of those if there's nothing like that
Anyway, what data do you want to recover from the phone??
Click to expand...
Click to collapse
Ya there's nothing like that unfortunately.
Mainly contacts and text messages. There's suspicions that her bf may have had something to do with her death and the police won't bother to do forensics on the phone so she asked if I could help.
I've been doing more research on this and have established that there is no way to get the LG855 (Marquee) into bootloader mode and no way to unlock the bootloader without getting past the keylock, I'm back to square one.
So my question remains, is there a way to convert a CWM recovery image (.img) file into a properly signed update.zip file that I can use the stock recovery to flash onto the phone from the SD card?
Thanks.
JZ_Hack_Nub said:
I've been doing more research on this and have established that there is no way to get the LG855 (Marquee) into bootloader mode and no way to unlock the bootloader without getting past the keylock, I'm back to square one.
So my question remains, is there a way to convert a CWM recovery image (.img) file into a properly signed update.zip file that I can use the stock recovery to flash onto the phone from the SD card?
Thanks.
Click to expand...
Click to collapse
I found this - which may help me sign the zip file.
http://forum.xda-developers.com/showthread.php?t=1966007
Still not sure if the .img file will flash properly without making changes to it. Any thoughts?
JZ_Hack_Nub said:
I found this - which may help me sign the zip file.
http://forum.xda-developers.com/showthread.php?t=1966007
Still not sure if the .img file will flash properly without making changes to it. Any thoughts?
Click to expand...
Click to collapse
You can never flash a zip file created by us from stock recovery.
You can do it from custom recovery.
However hard you try, you can never do it from stock recovery. It's waste of time
GokulNC said:
You can never flash a zip file created by us from stock recovery.
You can do it from custom recovery.
However hard you try, you can never do it from stock recovery. It's waste of time
Click to expand...
Click to collapse
Appreciated. I'm not one to give up though. I think I'll try this and let you know if it works. Thanks for all of your advice.
http://forum.xda-developers.com/showthread.php?t=732957