Need help and I assume I am stuck in a ‘soft brick’ state.
My Captivate does not advance past a kernel flash screen.
Upon boot, I receive the AT&T logo boot animation, then black screen, then with 5 seconds receive the splash screen of the Kernel developer (“Trident”). The phone remains stuck on this screen.
I can, however, initiate download mode and recovery mode (signs of hope).
In download mode I cannot get the device recognized by the multiple PCs I used to access the device by (the USB drivers are on the PC…..as evidenced through its functionality before). Consequently, and SDK / adb and ODIN* is of no help to me as an option to recover the device.
In recovery mode, I can apply sd card zips and have a few available (had several updates, superuser, kernels, etc downloaded prior to this device bricking) to apply. Of the zips available are;
CWM Recovery v3.0.0.5
Voodoo Lagfix
recovery CWM 2.5.1.2
SuperOneClick 1.9.5
ROM Kitchen Froyo ROM
11-254 Trident (Kernel Manager – ytt3r7 )
Click to expand...
Click to collapse
Backup file on device was from the day that the kernel was installed
After applying any of these zips (except the ROM Kitchen file) I will get an abort with the
“E:no misc partition” message.
>>>>>>>>>>>>>>once ROM Kitchen setup is applied it says "successful" then reboot it does the exact same thing as before (sticks in kernel splash screen)
For what its worth, this occurs with no SIM card and no SD card in the device.
*I have successfully used Odin on this device (usb functioning, recognized the device in Odin) and flashed/reset the device prior to this kernel problem.
** the reason I am in this position was because after receiving a warranty replacement (in stock 2.2 Froyo) I received the signature verification error. No amount of sidestepping this worked (I’ve read every page of the guides for this issue and they did not work) so I figured the easiest way around it was simply to replace the kernel (it wasn’t the bootloaders giving me errors). The phone was rooted, had superuser permissions, just could not apply any ROMs because of the sig verification.
To get a kernel to load (ROM manager / recovery mode zips did not work), I figured I would use market apps for this. I downloaded “Kernel Manager” from the market and applied the only kernel available (“Trident”). Once it applied the kernel, it left me stuck in the current stat I’m in.
*** I have read all previous "stuck in boot" threads and none of them have ANY troubleshooting methods available.
Just for clarification before further troubleshooting, you are putting the phone in download mode unconnected from the computer, starting up Odin, then connecting, correct? The only reason I ask is that I had some trouble with the computer seeing my messed up phone when I connected it prior to opening Odin.
correct - though, I've tried it in every sequence....ODIN (PC itself) doesn't see any USB device.
If I could get ODIN to recognize the device, I could wipe the phone and start over.
I guess my question is two-fold.
FIRST - Is it a correct assumption that this device is recoverable (not complete brick)?
SECOND - is there any way to fix the kernel loop from recovery mode?
1. I would assume yes, as you have activity from the phone.
2. Possibly. Hopefully you backed up (or don't care about) your apps, because most solutions at this point have a good chance of losing them. Also, from recovery, the first thing I'd do is a nandroid backup.
If you haven't tried this already, see if you can get Odin to recognize your phone while it's at the boot loop.
Next step would be trying to flash a kernel like Onix. You can do this one from CWM, so there's a chance it could fix your phone.
If that doesn't work, you could to grab a custom rom with a full wipe package (Firefly, for example) and see if you can run that from CWM. As it contains a kernel as part of the package, there is a chance you would be able to get your phone functional again.
I can't guarantee any of these methods, but they might help.
so - likely recoverable IF ODIN can recognize the device
BECAUSE there would be no other way to put the other kernels on the device (if you can't get the OS to load {past the kernel loop}
IF ODIN can recognize the device;
1. wipe/clear the device
2. load a different kernel through ODIN.
or is there another to load a kernel without ODIN?
Actually, from CWM recovery you can flash kernels (like the Onix one). Use the method you used before to get back there (holding V+/V-/power, i'm guessing), and assuming you have a way to get files to and from your micro SD card, just copy the onix kernel to your sd card and put it in your phone.
To flash the kernel, from the recovery menu select the "install zip from sd card" option, then "choose zip from sd card", and then navigate to where you saved it.
Assuming all goes well, it will overwrite the Trident kernel, and since Onix claims to work with stock roms, you should be back up and running.
jmtheiss said:
get files to and from your micro SD card, just copy the onix kernel to your sd card and put it in your phone. .
Click to expand...
Click to collapse
duh! (oy) that was genius....gawd, I can't believe I didn't even consider that.
T-H-A-N-K-S
I will try this
Ragin Caucasian said:
duh! (oy) that was genius....gawd, I can't believe I didn't even consider that.
T-H-A-N-K-S
I will try this
Click to expand...
Click to collapse
No problem. We all have those forest-for-the-trees moments.
Just as a heads-up, the onix kernel will be an intermediate step to a more final solution. The reason I say this is that it's based on I9000 source, so you would either need to flash an I9000 modem, or flash back to stock (overwriting the onix kernel). Either way wouldn't be difficult, but just something to remember.
i thank you for the feedback/help. This should work, unfortunately, it doesn't.
When attempting to load zip from sd-ext I get
E:no misc partition
Click to expand...
Click to collapse
when mounting the "/sd-ext" from CWM, I get
"E:failed to mount /sd-ext (no such file or directory)
Error mountin /sd-ext!
Click to expand...
Click to collapse
even if I attempt to format the /sd-ext, I get
Formatting /sd-ext...
E:format_volume: make_extf4fs failed on /dev/block/mmblk1p2
Error formatting /sd-ext!
Click to expand...
Click to collapse
So I'm stuck / dependent on ODIN (correct)?
Hmm.. oddly enough, I can't get the mount /sd-ext on my phone to work either (same message). Odin is looking like it might be your only option right now, but we can try a few more things.
I know it's a long shot, but have you tried the "mount USB storage" option on that page and seeing if your computer recognizes that?
Also, do the "wipe cache partition" from the top-level menu, and "wipe dalvik cache" from the advanced menu. Once you've done those, retry earlier steps and see if any of those clear things up.
Just out of curiousity, what version/versions of Odin have you tried?
jmtheiss said:
Hmm.. oddly enough, I can't get the mount /sd-ext on my phone to work either (same message). Odin is looking like it might be your only option right now, but we can try a few more things.
I know it's a long shot, but have you tried the "mount USB storage" option on that page and seeing if your computer recognizes that?
Also, do the "wipe cache partition" from the top-level menu, and "wipe dalvik cache" from the advanced menu. Once you've done those, retry earlier steps and see if any of those clear things up.
Just out of curiousity, what version/versions of Odin have you tried?
Click to expand...
Click to collapse
The sd/ext won't work unless you have an ext partition on your SD card.
Have you tried re installing your drivers?
If you can get to DL mode your comp. should recognize your phone.
I dunno.....
I've tried 2 different PCs (win7....32 and 64 bit environment) neither recognize the device. I keep getting the
E: no misc partition
Click to expand...
Click to collapse
anytime I doing anything with the sdcard (internal / external)
I've been using Odin3 (which is what I used to flash it originally)
Like I said, I can boot into Recovery Mode (get the internal menu) or boot into Download Mode (yellow sign 'downloading....do not turn off target!") but I don't think this really is doing anything because the PC never recognizes it and I can get into this mode whether I'm connected to a PC or not.
When I attempt to run Heimdall it runs and immediately crashes. This is what it displays
{
"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"
}
Heimdal Front end 1.1 used to work, but since the device isn't recognized, like ODIN nothing is presented to the application
I'm stumped. I just received this last Friday as a warranty replacement, I have 3 batteries and 2 usb cords, a rubber sleeve for the device willing to sell it all for $50 if anyone wants it.
Is the odin3 you're trying the one-click back to stock? Have you tried Heimdall? What version number shows up when you open it?
I used Odin3 v1.70 with my phone and had good luck. If you're using an earlier one, try using that one. If you're using v1.70, try an earlier version.
And to reiterate the earlier post, if you haven't tried uninstalling and reinstalling the drivers on your pc, that's worth a shot, too.
That dialog you're seeing with adb looks a lot like what happens if you run it without any arguments. Are you doing anything like "adb devices" or "adb reboot recovery"?
awesome!
Good news.....ODIN recognized the device
bad news......completely soft bricked the phone
I got the phone-<!>PC image and now the phone won't turn on again. great
I'll try the flux-capacitor jig fix sometime when I don't feel like strangling someone
Actually, you can use odin from the phone--!--pc screen. If you can get back there, try to flash the one click.
UPDATE
Bought the $10 jig (after my homemade resistor jig didn't work) - which works very well, btw.
* Uninstalled the USB drivers - reinstalled the USB drivers
* Used Odin3 1.8
* phone recognized by Odin.
* Flashed bootloader (what was originally wrong with the phone) and even a new ROM
Everything went FINE through Odin (first for me), even got a progress bar on my phone during the operation
now the phone is completely dead.
Will not give me the soft brick image.....can't go into download mode - nothing, completely unresponsive
$50....who wants it? This is a brand new phone just received as a warranty replacement....FOUR 1500m batteries, TWO USB cables, TV-OUT cable, and a rubber protective case
Related
Objective:
Thought I would create an app to try to make it easier to flash the ClockworkMod to your phone so you can get to recovery without having to use ROM Manager. This app will also let you revert back to Stock Recovery.
Flashing the custom recovery using NvFlash is the only way to ensure that in the case your phone will not boot up, you will be able to get into recovery to fix the issue / flash a ROM / restore from nandroid backup. That is what this app will do for you.
If you flashed the ClockworkMod recovery from ROM Manager it does not flash the recovery to your phone, it fake flashed it. The only way you can gain access to ClockworkMod recovery is through ROM Manager at that point. Using this method is the only way to flash recovery so it is persistent and accessible booting to recovery.
If you have already flashed through ROM Manager you can still proceed with this method. Flash Away!
(You can use both ROM Manager CWM and have the nvflashed version working together. You just access either or one at a time, having the nvflashed one means you can boot to CWM. Welcome to Tegra2)
Click to expand...
Click to collapse
Credits:
Thanks goes to player911, djmcnz, ctso(Chris Soyars) and mapin0518 for their contributions!
Thanks goes to omarsalmin for posting the guide and pulling it together for us!
Thanks goes to David Cogen at Unlockr for creating a video tutorial for this app!
Thanks goes to Krylon360 for his original modding work.
Thanks goes to RussUnderHill for his touch port.
And of course thanks (as always) goes to Koushik Dutta for developing ClockworkMod Recovery!!
-----------------------------------------------------------------------------------------------------------------------------
Krylon360's Updates to CWM 4.0.1.5
Ext4 Support
Internal SD ROM Flashing Support
Internal Nandroid Backup Support
Koush's updates to CWM 5.0.2.0
New option for flashing from the internal memory! When you choose "install zip from sd card" there is now an option "choose zip from internal SD card".
External Only Nandroid Backup Support.
EXT4 Support
Fixes a bug where root is sometimes lost during a ROM restore.
CWM Touch Port from P990 updates to CWM 5.8.1.3
Touch Interface
Experimental
Click to expand...
Click to collapse
Procedure:
If you came here first, go here and read the getting started before flashing this recovery: GETTING STARTED GUIDEhttp://forum.xda-developers.com/showthread.php?t=1060715
This process consists of 2 steps.
1. Install the windows driver.
2. Flash the Recovery using the OneClick App.
*** You will need to have .Net Framework 2.0 or above installed. ***
_________________________________________________________________________________________________
VIDEO:
You can watch a Video provided for us by the UnLockr for a walk-through of how to use the One-Click ClockworkMod Recovery Flasher. (Thanks Dave!)
Click on The UnLockr Image to watch the video:(Video is no longer relevant pertaining to entering recovery from boot. And the buttons you can click.)
_____________________________________________________________________________________________________________________________________________
Click to expand...
Click to collapse
One-Click ClockworkMod Recovery NvFlasher
{
"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"
}
Download:
One-Click-G2x-recovery-flasher-04-28-12.rar
Click to expand...
Click to collapse
****Warning I am not responsible if you brick your phone!****
Instructions:
Extract the package:
Extract the One-Click-G2x-recovery-flasher-04-28-12.rar to some location of your choosing.
Click to expand...
Click to collapse
Nvidia NvFlash APX Driver
Unlike a lot of Android phones out there the Nvidia Tegra2 chipset require additional drivers in Windows to support low level flashing.
Install APX Windows driver from APX folder.
(Windows x86 and x64 O/S Drivers):
****If you are running VmWare kill it.****
Remove the battery.
Plug in your USB cable to your PC.
Hold Volume Up and Volume Down at the same time keeping them held down.
Plug in the USB cable to your phone. (Keep the buttons held until Windows detects a new APX device.)
Open Device Manager in Windows and you should see "APX Device" listed with an error icon.
Right click on the APX device.
Select 'Update driver software'.
Select 'Browse my computer...'.
Select 'Let me pick...'.
Select 'Have disk'.
Browse to directory you extracted the *driver* software to: One-Click-G2x-recovery-flasher-04-28-12\APX.
Accept any warnings, including the big red alert (you may need to disable UAC).
Now in Device Manager under 'USB Controllers' you should have an 'NVIDIA USB Boot-recovery driver for mobile devices'.
If not, uninstall the driver, reboot, rinse and repeat.
Click to expand...
Click to collapse
Flash ClockworkMod Recovery
Remove the battery.
Goto NvFlash directory and Double Click "OneClickRecoveryFlasher.exe".
Make sure the USB cable is unplugged from your phone.
Hold Volume Up and Volume Down at the same time keeping them held down. (Keep them held until you see the "S/W Upgrade" screen on your phone after you complete step7!).
Plug in the USB cable to your phone.
Click the "Flash CWM" button of your choosing. If you own a External SD card I suggest to choose version 5.0.2.0. This gives you Internal and External SD Support for ROM flashing but has External SD Nandroid Backup Support Only! If you do not own a External SD Card choose version 4.0.1.5 what has full Internal SD support for flashing ROMS and Nandroid backup.
You should see it send a bunch of files to the device and the phone screen should say "S/W Upgrade - Please wait while upgrading...". Once the files are sent and the program is finished running in the command window, you can just pull the USB cord while it still says "S/W Upgrade - Please wait while upgrading...".
Put the battery back in and you can now boot into Recovery. (see below..)
Click to expand...
Click to collapse
Booting into ClockworkMod Recovery
Power off your phone.
Hold Vol Down + Power.
Keep holding them, as soon as you see a "Blue LG Graphic" logo let go of the buttons.
Click to expand...
Click to collapse
Restore LG G2x Stock Recovery
Flash Stock recovery only when you want to send your phone in to T-Mobile. Otherwise do not flash Stock recovery. Stay on ClockworkMod Recovery.
Remove the battery.
Goto NvFlash directory and Double Click "OneClickRecoveryFlasher.exe".
Make sure the USB cable is unplugged from your phone.
Hold Volume Up and Volume Down at the same time keeping them held down. (Keep them held until you see the "S/W Upgrade" screen on your phone after you complete step7!).
Plug in the USB cable to your phone.
Click the "Flash Stock" button.
You should see it send a bunch of files to the device and the phone screen should say "S/W Upgrade - Please wait while upgrading...". Once the files are sent and the program is finished running in the command window, you can just pull the USB cord while it still says "S/W Upgrade - Please wait while upgrading...".
Put the battery back and you are done.
Click to expand...
Click to collapse
Take it easy guys! I was a pleasure working with all of you.
I am moving on to another device Galaxy S IV.
PM me if you have any support questions.
Click to expand...
Click to collapse
Nice!! Thank you, sir!
Sent from my LG-P999 using Tapatalk
Niiiice
in the extracted folder,someone could place recovery-clockwork-3.0.2.7-p999.img in there and edit the FlashCWMRecovery.cmd to
nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 cwm-recovery-recovery-clockwork-3.0.2.7-p999.img and it should work,correct?
crazythunder said:
in the extracted folder,someone could place recovery-clockwork-3.0.2.7-p999.img in there and edit the FlashCWMRecovery.cmd to
nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 cwm-recovery-recovery-clockwork-3.0.2.7-p999.img and it should work,correct?
Click to expand...
Click to collapse
I will wrap it up and add it to my app.
EDIT: OK Done Deal
couldn't you have just done the same with a batch file or am I missing something?
could you set it to a variable that allows you to enter a file path to a recovery image and it just flashes that? rather than just the two hard-coded options
j2eubank said:
couldn't you have just done the same with a batch file or am I missing something?
Click to expand...
Click to collapse
Yes, but isn't this more pretty?
j2eubank said:
couldn't you have just done the same with a batch file or am I missing something?
Click to expand...
Click to collapse
Yes I could have and did. But for the new guys, they seem to like just clicking buttons. This should be newbie proof and easier in my opinion.
version 3.0.2.7 has been added.
could you set it to a variable that allows you to enter a file path to a recovery image and it just flashes that? rather than just the two hard-coded options
Click to expand...
Click to collapse
I will keep it updated with the latest versions. Soon there will be just one.
Awww thanks sweetie. I guess I have no reason to not upgrade to the lastest CWM.
I'll add this to my comprehensive "first-steps" thread.
I finally found a pc to recognize my phone and was about to try it the hard way, wow that was so fast and easy it almost scared me lol. Thanks so much for this.
Sent from my G2x
Thanks so much for your very kind and sensational work. I used and still use your one click root for the Vibrant. Your a gentleman and a scholar.
What is the difference in this 3.0.2.7 and the one flashed in rom manager?
TGA_Gunnman said:
Yes I could have and did. But for the new guys, they seem to like just clicking buttons. This should be newbie proof and easier in my opinion.
Click to expand...
Click to collapse
You should make it go get the files and extract them too...
Sent from my Xoom using XDA Premium App
Sweet, just upgraded from 2.4-2.7. Thanks!!
Painless! Thanks!
THANKS!
Awesome!!!! Thanks x10 man! ;D
oddities and/or errors ?
"reboot system now"
the First option in V. 3.0.2.7
powers off the device NOT reboot it
unless "reboot system now" is code for
Turn it off!
when you "reboot system now" (IE: Turn it off) with the USB plugged in
you get the the green charging screen with an oddity and/or error (o/e)
the o/e is that the Touch capacitive LED lights stay on
the only resolution is to unplug the USB till they go off OR turn on the phone
SECOND: (oops i think this is Thrid)
Holding down the Down volume key and power button to get into Recovery FAILS
if the USB is plugged into the phone
it will just keep refreshing the green battery charging icon
Boots into recovery fine if USB is not plugged in
OR plugging in the USB once IN recovery
BUT I'M NOT SURE THIS IS safe!
the last o/e is subjective BUT
seems to take a good 10-20 seconds longer to boot and recognize I'm on T-Mobiles network
it took SO Long the phone said "Emergency calls only" for about 5 seconds
this phone NEVER did that before!!!!
these o/e 's (oddities and/or errors) can't be normal and safe for my phone
can they ?
Rom Manager never caused these problems
that i get these o/e 's in a recovery program is kinda worrisome
PS:
OOPS ONE MORE O/E
because of the slow boot and not recognizing network for so long
i decided to run
"Quadrant"
i got 2686 Before flashing this recovery
NOW i get 2559
THIS is a big difference
and i have rebooted the system twice before running that benchmark
to make sure the recovery program just was not having a bad first boot, hence possibly lowering Quadrant scores
.
a1yet said:
"reboot system now"
the First option in V. 3.0.2.7
powers off the device NOT reboot it
unless "reboot system now" is code for
Turn it off!
when you "reboot system now" (IE: Turn it off) with the USB plugged in
you get the the green charging screen with an oddity and/or error (o/e)
the o/e is that the Touch capacitive LED lights stay on
the only resolution is to unplug the USB till they go off OR turn on the phone
SECOND: (oops i think this is Thrid)
Holding down the Down volume key and power button to get into Recovery FAILS
if the USB is plugged into the phone
it will just keep refreshing the green battery charging icon
Boots into recovery fine if USB is not plugged in
OR plugging in the USB once IN recovery
BUT I'M NOT SURE THIS IS safe!
the last o/e is subjective BUT
seems to take a good 10-20 seconds longer to boot and recognize I'm on T-Mobiles network
it took SO Long the phone said "Emergency calls only" for about 5 seconds
this phone NEVER did that before!!!!
these o/e 's (oddities and/or errors) can't be normal and safe for my phone
can they ?
Rom Manager never caused these problems
that i get these o/e 's in a recovery program is kinda worrisome
PS:
OOPS ONE MORE O/E
because of the slow boot and not recognizing network for so long
i decided to run
"Quadrant"
i got 2686 Before flashing this recovery
NOW i get 2559
THIS is a big difference
and i have rebooted the system twice before running that benchmark
to make sure the recovery program just was not having a bad first boot, hence possibly lowering Quadrant scores
.
Click to expand...
Click to collapse
confirmed working with windows 7 x64 home prem.. however it does power dwn with the reboot device now option.. did not do that with rom manager CWR 3.0.2.7... power off also powers dwn no reboot lol just though id check..
Flashing Roms with Odin and CWM from a stock phone and of course gaining root!
Warning!:I am in no way what so ever so help me Tom Cruise for any damage caused to your device. Although flashing is rather simple and straight forward you still run the risk of bricking your phone. Rooting and installing non-supported Roms does void and warranty you have with Verizon or Samsung. Warranty can be restored only if you flash back to stock firmware unrooted. Do NOT ever unplug your phone in the middle of a flash even if it appears to be locked up! Doing so will probably brick your phone and render it useless (well it sure would make for a fancy paperweight). ALWAYS make sure you have a reliable usb connection (take care of your usb cord and plug into a usb in the back of the machine). Download all Roms from credible sources and make sure they are complete and not corrupt. READ THE DIRECTIONS CAREFULLY. If you don't pay attention you can forever kill your phone!
"Updated, but waiting for DLSR camera for better pictures" T- probably next weekend
Everyone download these tools:
Windows Flashing utility called Odin: (if you decide to go this route
(I've included the links to both 1.85 and 1.83. Some users report errors while flashing and have better luck flashing with 1.83 or the other way around)
Odin3 1.85
Odin3 1.83
Samsung's phone drivers
Download
Latest Recovery CWM
Download
A way to open zip and .rar files I suggest Download"]WinRar[/URL]
Rom of choice! ~Only download ROMS of both odin and CWM zips from The Droid Charge forums. No other phones ROMs will work and you will break your phone.
Odin Roms *Also note only flash .md5 files
Stock latest ROM: Download *if you have stock fp1 ROM from verizon already, Follow instructions from CWM flashing "Part A"
Stock latest ROM "debloated" (no bloatware): Download
Tweakstock (custom developer created ROM): Found at this thread. Sometimes developers will make odin packages that contain a custom ROM,kernel,CWM packaged as on .md5 file. With these packages you can just flash with Odin and can omit flashing Recovery CWM
Download plain custom Rom
Download Packaged Rom that includes custom Kernel,ROM,CWM
CWM ROMS Flashable after Latest CWM is flashed to phone with the help of Odin
Stock Kernel
Download
Stock Debloated rooted
Download
SU Binary- Will "Root the device" No UI or system changes
Download
Tweakstock 2.0 ROM only~ 2.2 is current but you have to update through Tweaktools (a web based utility for modifying Tweakstock)
Download
Tweakstock with PBJ Kernel
Download
Tweakstock with PBJ Kernel and File system formatted to ext4 (improves read and write of the physical memory) you will lose all data
Download
Dictionary....
Odin 1.82or 1.85- Odin is the flashing utility you will run on your windows computer to flash your Droid charge. Pay close attention to what options you press and double check what you click as to prevent fatal mistakes. Remember to give Odin "administrator rights" by right clicking on the icon and selecting "Run as Administrator" if using Windows Vista or 7
Samsung Drivers- these are non-negotiable, download them and install them even if you think you already have them. They are necessary to connect your phone to your computer. Installing these drivers can elude problems that might occur when flashing with Odin
ROM of Choice- This is the Modified or stock "Operating system" if you will. These have to be flashed using either ODIN or CWM depending on what you downloaded.
Bloated (stock)- Contains all the (sometimes) useless garbage that both Verizon and Google put on your phone pre-loaded. This can sometimes cause lower performance and shorter battery life.De-Bloated- Basic app's and packages are loaded and nothing else. The OS is stripped of its extra goodies(usually preloaded apps like "Let's Play Golf"). This version tends to be faster and leaves you with maybe a little better battery (due to less apps running in the background), but lacks some features or programs you might want from the stock ROM
Latest CWM- This also needs to be flashed to your device. It is an added safety feature that can help when flashes go wrong. As well as it contains system tweaks. Also, some roms update through this. Flash this!
WinRar- A utility for your computer to unpackage many different file types. Specifically rar files and 7z files. The trial never stops working. Good program to have on your computer.
Kernel- Pretty much a under laying code that functions under the ROM. Generally this is where the Operating system is told it's limitations and how to do certain functions like charging, processor speeds, GPU speed, etc...
ROM- Stands for "Read only memory". this is because once it is flashed to the phone it cannot be edited or modified. This is where the majority of OS resides.
CWM- Stands for Clockworkmod. This is the Recovery program that will replace the stock program. The stock recovery isn't powerful enough and doesn't allow us to flash custom roms.
Ext4- A file system type. Similar to Fat32 or Ntfs filesystems found on windows hard drives. Stock file system is "rfs". While Ext4 may boost read and write speeds of the device, I find rfs to be more stable and produce less problems. Ext4 conversions will wipe all data.
PBJ Kernel A modified kernel by our dev Imnuts. you can find out more about it here at this >Thread
SuperUser- This is the elevated privilege level know as root. This allows you to read and write the system. This is why it is dangerous for rogue apps to gain root privileges. An app, SU manages apps that are allowed root and will prompt you when an app is requesting to gain elevated privileges.
If you would like more explained feel free to request a definition
****Now is the time to back up all your contacts. I recommend doing it with Google or by sending them to the Sim card. Verizon's backup isn't as reliable in my experiences. Some ROMs my not have Verizon's backup in them as they run in the background.****
What everyone must do: **Programs found above in Downloads section**
-Install Odin3 1.82 or 1.85 (1.85 recommended)
-Install Samsung Drivers
-Download CWM
-Create a folder on your computer to store all your phone download goodness
-Download whatever Rom you want to flash (CWM or Odin) this will take a while so might as well do it while you read.
Ok begin!: Choose you method for flashing! 8 I recommend Part A: CWM, It is the easiest and it harder to screw up your phone. Not to mention almost all new Roms are published as a flash-able .zip file not a odin .md5 file. HOWEVER, I also recommend learning Odin as if anything goes wrong Odins the only program that can save the day( Kind of ironic that it's also the program that can kill your day if you mess up. Don't fear though, if you follow the directions you will be fine).
NOTE: When you flash with Odin you will Lose all data, Also, With CWM flashes I HIGHLY recommend wiping and restoring to factory, but it is not necessary. (less problems occur after flashing between ROMS)
Part A= CWM Method or Part B= Odin Method
Pre-Method- CWM flashers do this first
*omit for Odin flashers.
1. Confirm all downloads are complete and move files to desktop or a dedicated folder.
{
"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"
}
3. Open location where you downloaded Odin to and drag Odin icon to desktop
4. Install samsung Drivers (I'm guessing you all are capable of doing this without explaining but if you need help let me know)
5. Open Odin 1.82
6. Turn OFF your phone
7. Now put your phone in download mode
Hold the "Volume down" key and plug phone into usb.
Alternative: Hold Volume Down and press power.HINT: if that is a no go, take out the battery. While holding volume down, plug your usb cable in. Download mode should appear. Put battery back in.
8. Connected to computer via a good OEM usb cable if you haven't done so already. (it is recommended to use the usb at the back of your computer, If flash fails switch to a different one and try again)
9. Notice Odin will pick up the device.
First bottom white slot should now be yellow with a "[COMx] x~ notates any number can be here
10. IMPORTANT: Check PDA and only PDA (under Files [Download])
11. Click PDA button
12. Browse to where your "Recovery MD5" ~you should have downloaded this in the beginning of the post.
13. Double check that you only selected PDA
14. Triple check you only checked PDA
Re-Partition--- Unchecked
Flash Lock--- Unchecked
Auto Reboot--- Checked if you would like your charge to reboot after the flash
F. Reset Time--- Checked
phone EFS Clear--- Unchecked
Phone Bootloader Update--- Unchecked
BOOTLOADER--- Unchecked
PDA--- Checked
Phone--- Unchecked
CSC--- Unchecked
15. Now click Start button
16. WAIT
17. yellow bar should go green and a message should display on the page saying it Passed
18. If flash "FAILED" don't fret. Try it again. play around with flashing with and flashing without the battery in. If continues to fail re-download the Recovery and try again.
19. Custom "Recovery" now installed on device
20. Reboot phone if it hasn't done so already
If flashing process fails or you boot loop (Samsung logo keeps appearing)...
Turn off your phone or remove the battery.
Place phone in download mode (volume down then plug phone into a power source)
Put battery back in
reflash in odin
Pre-Method Finished
Method "A" CWM Flash
1. Complete the Pre-Method
2. If you are just rooting and do not want to flash a custom rom download "Su Binary zip" Here.
If not proceed to step 3
3. While device is on, Connect usb to computer
4. On your Droid Charge, Press "Connect storage to PC" button
5. Click "Continue without scanning" on your PC, if it shows up
6. Browse to the Droid Charges SD card via " Computer" if it doesn't automatically launch
7. Place your "Su Binary" (if just rooting) or Rom of choice either on the root of the card or in a folder of your choice
8. Turn off your phone
9. Now reboot into CWM Recovery on your phone
To boot into Recovery- Hold: Power+ Volume up+ Home buttons when phone is "OFF" until samsung is displayed. Boot should then take you to CWM should be a cyan colored menu screen.
10.Navigate to "Mounts and Storage". (using the volume buttons and power to select)
11. Select mount /System (it will change to /unmount when properly mounted)
12.Select mount /Data (I do this just in case)
13. Select +++++Go Back+++++
14. Select "Install zip from sdcard
15. Find you Rom or the Su Binary zip, select it
16. Select Install
17. WAIT until flash finished
18. select "reboot system now"
19. Let system reboot (will take longer than normal on first boot)
20. Congratulations and pat yourself on the back for a new rooted and\or a fresh new custom ROM
Remember you can substitute the Rom with another ROM, a Kernel, updated CWM, Or any other updated .zip file designed for the charge
Method B
1. Confirm all downloads are complete and move files to desktop or a dedicated folder.
2. Install WinRar to unzip or unrar .md5 file if applicable
3. Open location where you downloaded Odin to and drag Odin icon to desktop
4. Install samsung Drivers (I'm guessing you all are capable of doing this without explaining but if you need help let me know)
5. Open Odin 1.82
6. Turn OFF your phone
7. Now put your phone in download mode
Hold the "Volume down" key and plug phone into usb.
Alternative: Hold Volume Down and press power.HINT: if that is a no go, take out the battery. While holding volume down, plug your usb cable in. Download mode should appear. Put battery back in.
8. Connected to computer via a good OEM usb cable if you haven't done so already. (it is recommended to use the usb at the back of your computer, If flash fails switch to a different one and try again)
9. Notice Odin will pick up the device.
First bottom white slot should now be yellow with a "[COMx] x~ notates any number can be here
10. IMPORTANT: Check PDA and only PDA (under Files [Download])
11. Click PDA button
12. Browse to where your Rom is located ~you should have downloaded this in the beginning of the post.
13. Double check that you only selected PDA
14. Triple check you only checked PDA
Re-Partition--- Unchecked
Flash Lock--- Unchecked
Auto Reboot--- Checked if you would like your charge to reboot after the flash
F. Reset Time--- Checked
phone EFS Clear--- Unchecked
Phone Bootloader Update--- Unchecked
BOOTLOADER--- Unchecked
PDA--- Checked
Phone--- Unchecked
CSC--- Unchecked
15. Now click Start button
16. WAIT
17. yellow bar should go green and a message should display on the page saying it Passed
18. If flash "FAILED" don't fret. Try it again. play around with flashing with and flashing without the battery in. If continues to fail re-download the Recovery and try again.
19. Custom Rom should now installed on device
20. Repeat but now flash the custom recovery and a custom kernel if your Rom was not a "Packaged" Rom
If flashing process fails or you boot loop (Samsung logo keeps appearing)...
Turn off your phone or remove the battery.
Place phone in download mode (volume down then plug phone into a power source)
Put battery back in
reflash in odin
Tips:
If you lose "root" flash the "SU Binary" through CWM
Be patient and pay attention!
~Made for noobs by a noob
if reflashing doesnt work revert to DaleV's unbricking tutorial HERE
CREDITS: A BIG Thank You!- I am not asking for donations, but please consider donating to these great developers
IMNUTS- created the recovery
P3Droid- Provided original leak to us all
danalo1979- Provided a nice reference to links and compiled recovery into ROM for ease of use.
DaleV- recovering after fail tutorial http://forum.xda-developers.com/showthread.php?t=1026746
Other Devs- that are working around the clock to tweak these ROMs and make them better
awesome
Very nice explanation. This was desperately needed for Newbies. You should also put up the resolve for those that get the "manual movi" thingy and think they briked their phone.
Mig1234 said:
Very nice explanation. This was desperately needed for Newbies. You should also put up the resolve for those that get the "manual movi" thingy and think they briked their phone.
Click to expand...
Click to collapse
I would be happy to, Once I'm done with the flashing part I will look it up. I've never encountered it myself, but research can hurt.
Scary..great explanation...the only thing I will add is to go into download mode...you do not have to press the power button....if you hold down the volume down button...it will go into download mode.......
What's the skinny on removing the SIM card?
I have seen it mentioned that it must be removed, that it interfered with odin-flash when removed, and not mentioned at all. Any definitive answers? I have personally odined both with it in and out, and have not encountered difficulty either way. Sometimes battery out works, sometimes it fails, same with different usb ports. Fickle little device, but it is forgiving
hogowner said:
Scary..great explanation...the only thing I will add is to go into download mode...you do not have to press the power button....if you hold down the volume down button...it will go into download mode.......
Click to expand...
Click to collapse
oo hey your right. well you need to tap power if it is off
budsy said:
What's the skinny on removing the SIM card?
I have seen it mentioned that it must be removed, that it interfered with odin-flash when removed, and not mentioned at all. Any definitive answers? I have personally odined both with it in and out, and have not encountered difficulty either way. Sometimes battery out works, sometimes it fails, same with different usb ports. Fickle little device, but it is forgiving
Click to expand...
Click to collapse
Honestly I always leave it in unless the ROM developer specifies otherwise. I think it has something to do with updating the radio. But I am not positive. A developer or one with more knowledge of flashing probably could tell you. I have seen though if it is in it can cause problems, through reading on the forum. But flashing with stock or leaked firmwares leaving it in shouldn't bother it
For me I've never been able to flash with battery out. A couple flashing tutorials have told me to leave it out however personally i have to leave it in.
Thankyou for mentioning the usb. I probably should mention it is sometimes better to use a back usb port.
are photos too big?
Great reference tool!!! Will keep in favorites...
ok coming from a noob,
This is perfect.
Had my DC for 1 day, then rooted, and running froyo humble 1.3,
Tonight, now the GB 2.3.4.
This really should be sticky'd.
Thanks,
John
Ravanous said:
ok coming from a noob,
This is perfect.
Had my DC for 1 day, then rooted, and running froyo humble 1.3,
Tonight, now the GB 2.3.4.
This really should be sticky'd.
Thanks,
John
Click to expand...
Click to collapse
Thanks good to hear. Just be warned 2.3.4 does have some issues that need to be worked out. Not that serious, but you may wish to go with the Humble ROM as you would be getting more support and updates to improve the system over the stock 2.3.4.
Good Luck!
Jeff
works great
I used the EP1H rom.. debloated verzion, err version.. ok bad joke.. so far so good.. i do like the go launcher, but will go back to my favorite launcherpro.. i'll reply after i've had time to post any issues i may come across.. got so used to rom manager with original droid, odin is different, i'll give it that
Once you have the firmware build you want, being froyo EE4 or gingerbread EP1G\H, you can pretty much just flash roms with zips in CWM. Less I touch Odin the better.
please sticky this thread
Thanks for this very informative and helpful post!
The Droid Charge was funny, the only way to get into DL mode was to remove the battery, plug in the USB and press vol. down. But the ODIN process would fail until I inserted the battery after the fact.
guruleenyc said:
Thanks for this very informative and helpful post!
The Droid Charge was funny, the only way to get into DL mode was to remove the battery, plug in the USB and press vol. down. But the ODIN process would fail until I inserted the battery after the fact.
Click to expand...
Click to collapse
Indeed. I have never been able to flash with the battery out. The droid charge can be finicky at times
jamesnmandy said:
please sticky this thread
Click to expand...
Click to collapse
You probably wont see many stickies on this site. Just because we have a "Look here First" thread that this is located in
scarygood536 said:
You probably wont see many stickies on this site. Just because we have a "Look here First" thread that this is located in
Click to expand...
Click to collapse
I spent a good 20-30 minutes searching manually and using the site search feature before I finally came across this thread. I didn't come looking for GB info specifically. I was looking for a recent Odin download link. True, in the stickies there is a thread with packs which include Odin, along with 650Mb of other files I didn't want. Odin is a 500Kb file and is essential to all flashing at some point. That's why I feel a sticky is certainly warranted because it contains GB info which is where we are going and Odin links as well.
should voodoo be completely removed from phone before the procedure? and thanks awesome thread
SFniner415 said:
should voodoo be completely removed from phone before the procedure? and thanks awesome thread
Click to expand...
Click to collapse
Nope I didn't have to. As long as you are going to a stock ROM and not a modified ROM (gummycharged or Humble...) you should be good to go. Just be sure Wipe data and cache (i think you don't even need to do this but do it just in case) Voodoo doesn't even work with GB, so if you download a packaged version (includes CWM and is rooted) of GB you are good to go, However if you download just the firmware itself and no the recovery, make sure you do download a updated CWM from IMNUTS post that is compatible with GB.
as I have promised here is are the first 3 custom ROMs for the gogear connect 3 8gb. if there is interest i will work on a few ROMs for the 16gb version also.
The way of installing roms on this device is a little different than most people are used to so i have included instructions
(with pictures this time!) but because of this way to do it it also makes this device almost brick proof and easy to fix.
before we start make sure your battery is at least charged 50%
THIS WILL DELETE ALL OF YOUR DATA EVEN THE STUFF ON THE "SD CARD"
In this guide i will be using the AndroidGeneric Rom for the example.
be sure to look in the rom package to see if i have given any extra instructions for the specific rom
1. Download the MfgTool Package at the bottom of this post. also download the rom package you wish to install.
2. extract the MfgTool Package somewhere onto your computer
3. extract the rom Package somewhere on your computer also.
4. now take the actual rom folder (in this case the AndroidGeneric folder) and put it into the profiles folder in MFG tool folder
5. Turn off your MP3 Player Compleatly
6. now with your player still turned off hold Volume Up and plug it into your computer.
7. dont let go of Volume Up untill a new device named SE Blank ELVIS shows up on your computer
{
"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"
}
8. install the driver located in the Drivers folder inside the MfgTools Folder (the driver isnt signed so you have to click a popup allowing it to install, x64 users may need to turn off driver signing to get this to work)
9. After Thats Done open MfgTool.exe
10. once Mfg tool is open click on the Options drop down menu from the menu bar and click Configuration
11. in the window that pops up Select the USB Ports tab. then scroll down the menu untill you find "Freescale i.MX51 USB BulkIO Device" and put a check mark in the check box next to it. then select ok.
12. now your back to the Mfg tool main window. Check the Profile drop down menu to make sure it is on the rom you want. then hit start.
13. it will install the rom you selected. when you get to the part where it says "please connect device" and the stop button is red it is done installing. hit the stop button and unplug your mp3 player from the computer.
14. turn on your mp3 player with its new rom. it may take a little bit longer than usual to start up but thats only because its for the first time.
15. you are done unless there are more instructions with the rom.
for people that have already done this, here is a set of instructions to install differant roms
1. extract the rom Package somewhere on your computer.
2. now take the actual rom folder (in this case the AndroidGeneric folder) and put it into the profiles folder in MFG tool folder
3. Turn off your MP3 Player Compleatly
4. now with your player still turned off hold Volume Up and plug it into your computer using the same usb port that you used the first time
5. dont let go of Volume Up untill you hear the beep of the computer recognizing the device.
9. After Thats Done open MfgTool.exe
12.Check the Profile drop down menu to make sure it is on the rom you want. then hit start.
13. it will install the rom you selected. when you get to the part where it says "please connect device" and the stop button is red it is done installing. hit the stop button and unplug your mp3 player from the computer.
14. turn on your mp3 player with its new rom. it may take a little bit longer than usual to start up but thats only because its for the first time.
15. you are done unless there are more instructions with the rom.
Here Are the Files:
MfgTool
Download
Custom rom AndroidGeneric with root and all the gogear modifications removed and the regular android files installed.(regular android boot screen also) (radio app is from original rom)
Download
Original Rom with Root
Download
Original Rom With Root and all the bloatware removed
Download
Do I need to be rooted already to follow these steps or it doesn't matter?
you dont need to be rooted this can be used as an alternative to rooting
thanks for the guide im rooted running stock rom minus bloat that u uploaded
im working on a pretty cool ROM. ill release it when i get all the bugs out. it will be completely different from the roms i have posted so far. im working on a mix between the honeycomb blue accents and ipod touch styling with the page transitions form ICS.and custom fonts. im using the MUIUI Music app to give it a mor ipod touch feel. when im done testing the rom ill post it up here for you guys.
at this moment in time i am unable to continue in develpoment on the device i had to sell it because of some financial issues. i will post the rom i made as it stood the day i sold the device. it was a pretty good rom and it was pretty straight foward. i will post it online within the next few days
I have a 16GB version and would love to install a custom ROM on it. Please count me ad interested in getting a 16GB version. I am also running a 64bit Version of Windows, does your guide support this, or only 32bit systems?
thanks! this gogear is my first android device.. i am currently running your -bloat rom. i would like to create my own roms. i was wondering though how is it you create these rom?? is there a tutorial somewhere about this?
Thank you for creating these ROMS. Can you confirm what build they are based off of?
The latest build from Phillips is:
Android Version: 2.3.3
Kernel Version: 2.6.35.3-00054-g1e2e42c
Build Number: GGC3.01.06.10
I am guessing that your builds are based off of these, but would like to make sure before I flash something. (This is good info to have in the OP in some form.)
Have one coming
When I get mines on the 12th ogf february i may see if i can make roms
HGStone said:
thanks! this gogear is my first android device.. i am currently running your -bloat rom. i would like to create my own roms. i was wondering though how is it you create these rom?? is there a tutorial somewhere about this?
Click to expand...
Click to collapse
you need a linux computer and the android sdk to develope and the adb drivers installed.
After following this guide, my GGC became bricked
MfgTool would stop at "Formatting op6 partition" before showing me "Update error -65535-" and after unplugging/plugging back in it shows up as "Linux File-Stor Gadget" and I can't access it from Windows because it says "Please insert a disk into drive X:" (I changed the drive letter so I wouldn't get confused)
It turns on but doesn't get past the Philips logo. I tried repairing it with songbird but I always ends with an unexplained error.
I tried flashing it with mateo1212's OriginalRooted and AndroidGeneric roms as well as the original GGC3 rom found in C:/Program Files/Philips/Philips Songbird Resources/Firmware/SA3CNT/SA3CNT.zip (extracted the archive to MfgTool/Profiles and named it SA3CNT) and still no luck, ending in the same error mentioned above.
Can anyone help? Philips is already sending me a replacement (I played dumb with them) but if I could save this one it would be great...
Can anyone help me with this? I`m doing everything as the instructions say, but the MfgTool wont update the rom.
It starts working on the device, but gets stuck on error message (operation time out). After that it starts all over by itself.
One possible reason could be that the mfgtool version provided here was not working properly on my win7 (64bit). To solve this I downloaded another version of the program form the authors website.
The reason I had to change version was that the mfgtool crashed everytime I entered the "configuration" menu and the "usb ports" submenu.
All the help is much appreciated!
yep
superkidmax said:
After following this guide, my GGC became bricked
MfgTool would stop at "Formatting op6 partition" before showing me "Update error -65535-" and after unplugging/plugging back in it shows up as "Linux File-Stor Gadget" and I can't access it from Windows because it says "Please insert a disk into drive X:" (I changed the drive letter so I wouldn't get confused)
It turns on but doesn't get past the Philips logo. I tried repairing it with songbird but I always ends with an unexplained error.
I tried flashing it with mateo1212's OriginalRooted and AndroidGeneric roms as well as the original GGC3 rom found in C:/Program Files/Philips/Philips Songbird Resources/Firmware/SA3CNT/SA3CNT.zip (extracted the archive to MfgTool/Profiles and named it SA3CNT) and still no luck, ending in the same error mentioned above.
Can anyone help? Philips is already sending me a replacement (I played dumb with them) but if I could save this one it would be great...
Click to expand...
Click to collapse
same man
superkidmax said:
After following this guide, my GGC became bricked
MfgTool would stop at "Formatting op6 partition" before showing me "Update error -65535-" and after unplugging/plugging back in it shows up as "Linux File-Stor Gadget" and I can't access it from Windows because it says "Please insert a disk into drive X:" (I changed the drive letter so I wouldn't get confused)
It turns on but doesn't get past the Philips logo. I tried repairing it with songbird but I always ends with an unexplained error.
I tried flashing it with mateo1212's OriginalRooted and AndroidGeneric roms as well as the original GGC3 rom found in C:/Program Files/Philips/Philips Songbird Resources/Firmware/SA3CNT/SA3CNT.zip (extracted the archive to MfgTool/Profiles and named it SA3CNT) and still no luck, ending in the same error mentioned above.
Can anyone help? Philips is already sending me a replacement (I played dumb with them) but if I could save this one it would be great...
Click to expand...
Click to collapse
Hi,
I also want to change rom but after reading you, I'm afraid now.
Have you take a look to this thread: http://forum.xda-developers.com/showthread.php?t=1396085
It says on the first post that:
I Have Figured out how to unbrick and flash this device if you have Messed it up while having root privileges. this method can also be used to install custom roms once some are made. if people need the repair/flash method or wanna work on roms let me know in the comments and i will post the files and guides needed for it.
Click to expand...
Click to collapse
Good luck.
I am new to this forum and normally would not dream of rooting so I have printed the instructions and thoughly read them. I wish to use the Original ROM rooted and with bloatware removed. I understand the instructions except for step 8. How do I install the driver?
Anyone know why some people report failure and bricked devices? I would hate for this to go wrong!
Where is everyone?
GraySan said:
I am new to this forum and normally would not dream of rooting so I have printed the instructions and thoughly read them. I wish to use the Original ROM rooted and with bloatware removed. I understand the instructions except for step 8. How do I install the driver?
Anyone know why some people report failure and bricked devices? I would hate for this to go wrong!
Click to expand...
Click to collapse
Hi, just follow the guideline it will be ok, as to step 8, in the device manager you should right click the SE Blank ELVIS and manually install the driver, wait a moment it will successfully install the driver, after that you can follow next step.
By the way, I just flashed under Win7 64, everything went smoothly when just follow the guideline. Thank you mateo1212!
For people with bricks because of this
PPl don't be scared if you get bricked, i try at first and i got bricked, my device was in a loop and did not start, at the beginning just was showing a black screen then i tried to turn it on and it was in a loop.But i manage to recover it! This is what i did to recover it:
Download the mfgtool provided in this post.
Download the android files to flash provided also here
Put the device in flash mode or whatever is called the state when you power on the device with the volume up key pressed. ( for me this was specially hard since it was doing a loop, what i did was to push the reset button with a needle, then as soon as release the reset, push the power button and the volume up, and then connect the usb cable... create your own way to do it, just keep in mind you need to have your device booted in this kind of service mode ( vol up and power) before proceed.
Then just click on start and wait... it did it successfully this time...
Obviously you need to put your rom folder in profiles and everything just as explained in this guide.
THANKS, I UPDATED MY DEVICE WITH ROOT! :cyclops:
---------- Post added at 05:48 AM ---------- Previous post was at 05:41 AM ----------
GraySan said:
I am new to this forum and normally would not dream of rooting so I have printed the instructions and thoughly read them. I wish to use the Original ROM rooted and with bloatware removed. I understand the instructions except for step 8. How do I install the driver?
Anyone know why some people report failure and bricked devices? I would hate for this to go wrong!
Click to expand...
Click to collapse
In my case it failed just after it erase everything with no reason, however the same method worked the second time so i think is not risky to try, you are going to be able to install it eventually following this method. For more info see my other post. Cheers.
fail to root it by supper click try download flash
I try to use supper click to root it but failed the information is like below
step #7 WaitForDevice ................short name = mixed, utf8, errors = remount-ro)/dev/b.
any idea about it?
Hello,
Not sure what to do at this point. I have a Creative ZEN Touch 2, device from 2010. Creative told me the bootloader is locked.
It's running Froyo, rooted.
Little background. Would love to.. maybe "try" to port Clockworkmod on it, or maybe just reflash the original kernel, because mine got corrupted somehow (Even then, not sure how. Boot.img packing doesn't seem to be standard!).
- The device does not have fastboot;
- It contains Android Recovery 3e, which does not allow flashing unsigned ZIP files. Tried to sign the ZIPs, not working I guess.
- /Recovery and /Boot seems to be one single 10MB partition (Doesn't look good);
- I managed to get ADB working, detecting the device correctly. Required tweaking.
- No custom ROMs, recoveries, kernels exists. No softwares either provided by Creative.
I do have the original bootloader files, extracted from an official update. If I could somehow replace these, I could perhaps fix the kernel. I have attached the files from the bootloader if people want to take a look. env.bin have been renamed to env.img, u-boot-no-padding.bin has been renamed to u-boot-no-padding.img and uImage has been renamed to uImage.img.
But what now? How am I suppose to unlock the bootloader completely on my own without any software provided ??
If I wanted to attempt the unlock, taking the risk of a hard brick, what shoud I try, how should these files be opened? In a HEX editor? How do people acheive the unlock first, that's what I would like to know. The point is really to find a flaw in the bootloader, correct? (I suppose I don't have the brain to figure this out. But if the answer is that easy because the device is outdated...)
I've read that sometimes it can be impossible if the manufacturer does not provide a way to do it. Am I correct, wondering that since the device is from 2010 (Originally had Eclair), such technology would be really primitive and could be a breeze to find a flaw on such a outdated device? Easy perhaps for not me, but someone else? Is the year of the device completely unrelated?
I would like to know more about this, how this is done (HEX editing?) and if it's really a dead end (Considering also that the device is from 2010).
EDIT: But does the device has Fastboot, somehow? I mean, how did Creative flashed the device from the factory if I cannot reach anything at the bootloader level?! No Download Mode, no Fastboot, no Emergency Mode (Just Android Recovery 3e. Still had to be flashed from somewhere. Jtag?) ??? How can I confirm Fastboot is not there? adb reboot bootloader just reboot the phone normally even with root access.
Asking this, since my other phone, LG P500 does have Fastboot, but it must be manually enabled with a software (And even now, the ZEN Touch 2 has no software availible to do this).
Thank you very much!
GameX2 said:
Hello,
Not sure what to do at this point. I have a Creative ZEN Touch 2, device from 2010. Creative told me the bootloader is locked.
It's running Froyo, rooted.
Little background. Would love to.. maybe "try" to port Clockworkmod on it, or maybe just reflash the original kernel, because mine got corrupted somehow (Even then, not sure how. Boot.img packing doesn't seem to be standard!).
- The device does not have fastboot;
- It contains Android Recovery 3e, which does not allow flashing unsigned ZIP files. Tried to sign the ZIPs, not working I guess.
- /Recovery and /Boot seems to be one single 10MB partition (Doesn't look good);
- I managed to get ADB working, detecting the device correctly. Required tweaking.
- No custom ROMs, recoveries, kernels exists. No softwares either provided by Creative.
I do have the original bootloader files, extracted from an official update. If I could somehow replace these, I could perhaps fix the kernel. I have attached the files from the bootloader if people want to take a look. env.bin have been renamed to env.img, u-boot-no-padding.bin has been renamed to u-boot-no-padding.img and uImage has been renamed to uImage.img.
But what now? How am I suppose to unlock the bootloader completely on my own without any software provided ??
If I wanted to attempt the unlock, taking the risk of a hard brick, what shoud I try, how should these files be opened? In a HEX editor? How do people acheive the unlock first, that's what I would like to know. The point is really to find a flaw in the bootloader, correct? (I suppose I don't have the brain to figure this out. But if the answer is that easy because the device is outdated...)
I've read that sometimes it can be impossible if the manufacturer does not provide a way to do it. Am I correct, wondering that since the device is from 2010 (Originally had Eclair), such technology would be really primitive and could be a breeze to find a flaw on such a outdated device? Easy perhaps for not me, but someone else? Is the year of the device completely unrelated?
I would like to know more about this, how this is done (HEX editing?) and if it's really a dead end (Considering also that the device is from 2010).
EDIT: But does the device has Fastboot, somehow? I mean, how did Creative flashed the device from the factory if I cannot reach anything at the bootloader level?! No Download Mode, no Fastboot, no Emergency Mode (Just Android Recovery 3e. Still had to be flashed from somewhere. Jtag?) ??? How can I confirm Fastboot is not there? adb reboot bootloader just reboot the phone normally even with root access.
Asking this, since my other phone, LG P500 does have Fastboot, but it must be manually enabled with a software (And even now, the ZEN Touch 2 has no software availible to do this).
Thank you very much!
Click to expand...
Click to collapse
i rooted one of these a while back if it helps here is how i did it..
1. Install "z4root.1.3.0.apk". (i used adb to install "adb install z4root.1.3.0.apk")
2. Open Z4root and click permanent root, it will take a bit to complete, then it will restart your Zen.
You should now be rooted and have access to stuff which may help you further? i did have a custom recovery for it somewhere on my linuxbox i will have a dig around on my hdd an see if i can find it..
thank you
Yes, I'm definitely rooted using Z4root as well.
This is interesting about the custom recovery, I found nothing. Not sure, considering Boot and Recovery seem to be a single partition, this could be dangerous.
Creative told me the bootloader was locked, so even if I flashed that custom recovery, I would get an error I guess?
But still, I have no way to verify if what Creative said was true, if the bootloader really is locked. Could be.
Thanks again for looking
Sent from my SGH-I337M using XDA Free mobile app
Inside 4ndroid said:
i did have a custom recovery for it somewhere on my linuxbox i will have a dig around on my hdd an see if i can find it..
Click to expand...
Click to collapse
Found anything new yet?
You can sign flashable zips with te test keys so you can flash them through stock recovery.
You have to have the software called signapk.jar. Search for it.
root-expert said:
You can sign flashable zips with te test keys so you can flash them through stock recovery.
You have to have the software called signapk.jar. Search for it.
Click to expand...
Click to collapse
Previously I think I used to flash an update.zip with absolutely no signature, so I think it would fail immediately to flash.
Now I do believe I've signed the file with sign-apk.jar, but still not working. Now, the update package open along with a progress bar, but 10 seconds later, it's still rejected, with a new error message stating "Failed to verify whole file signature".
{
"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"
}
So it does check for a signature huh?
Weird because this update.zip was extracted from an official APK firmware update.
It check if the signature of the ZIP match the signature of, huh, the manufacturer, Creative?
Any way I could find out what is the valid signature to make it match properly?
Or would I just have to try again, and re-sign the ZIP with a different software?
EDIT: Here's the untouched update.zip file if you want to take a look.
https://dl.dropboxusercontent.com/u/67605655/update.zip
Or maybe you can try and sign it for me? Have I done something incorrectly?
Thank you
@GameX2 i have attached a signed zip. Try to flash it. This file is from the vendor? If this file is from the cendor then it should have been installed without any problems.
As far as the bootloader is concerned, i don't if it is locked. You have to boot to bootloader mode (if any??). If you want to unlock it and the vendor deosn't provides any tools then, yes, you have to hack it. This is done by reverse enginnering and as you said you have to find an exploit. Or maybe you can flashed an "unlocked" bootloader if the partition isn't signed by the vendor.
But if you don't have fastboot you can f;ash anything. Jtag is solution but it is difficult and you need expensive equipment.
root-expert said:
@GameX2 i have attached a signed zip. Try to flash it. This file is from the vendor? If this file is from the cendor then it should have been installed without any problems.
As far as the bootloader is concerned, i don't if it is locked. You have to boot to bootloader mode (if any??). If you want to unlock it and the vendor deosn't provides any tools then, yes, you have to hack it. This is done by reverse enginnering and as you said you have to find an exploit. Or maybe you can flashed an "unlocked" bootloader if the partition isn't signed by the vendor.
But if you don't have fastboot you can f;ash anything. Jtag is solution but it is difficult and you need expensive equipment.
Click to expand...
Click to collapse
Thank you for that;
I've tried your update.zip, strange as it's still not working. In that case, no progress bar shows up, like last time (It's like if the ZIP wasn't signed at all?):
Code:
-- Install from sdcard --
Finding update package...
Opening update package...
Verifiying update package...
E: signature verification failed
Installation aborted.
For info, when I've tried signing the ZIP myself using different tools such as sign-apk.jar and Sign-Em, I got a sightly different message along with a progress bar, shown in my last message.
That file is from the vendor, sort of, the firmware update is provided as an APK file. I've tried using that APK to upgrade the version, which is on 2.00.23 and there is a final release, 2.00.38, which brings almost nothing new, but being able to upgrade would reflash the original kernel and fix all these issues in fact... But when I try launch the APK, it's just not working, I get "The installer is not intended for your device" (Is that a joke ???)
Like this:
Huh. No clue, I have unrooted the device, nothing. I even decompiled the APK file with APKTools to see which conditions the APK check. Not sure, I'm not a programmor, but I saw a reference of build.prop, so I've restored the original build.prop file from the official firmware, still nothing.
Here's where you can download the 2 official firmwares. So they definitely are from the vendor.
http://support.creative.com/Product...MP3+Players&prodID=20275&prodName=ZEN+Touch+2
Regarding the update.zip file, that's also why I said "sort of", because no update.zip file is provided, it's an APK file. Instead, I've followed the instructions from this thread:
http://www.anythingbutipod.com/forum/showpost.php?p=610226&postcount=36
Allright,
I even didn't believe this couple of months ago when I broke my zen touch, but here is the cure which will get you a plain factory reset from the situation we all got into following these steps:
1) download firmare upgrade (the .apk file) from the official creative page
2) rename it to "firmware.zip"
3) extract from this archive a file from the "assets" folder called "data"
4) rename this "data" file to "update.zip"
5) copy this "update.zip" to your microSD card and put it into your Zen Touch device
6) start (or reboot) your Zen Touch
7) open the main screen and if you're lucky enough, you'll see a "firmware upgrade detected" dialogue. if so, allow the reboot and let your device be upgraded
8) in case you don't get the dialogue above, try to put the microSD card into your Zen Touch while running. and hopefully you'll be given the possibility for a firmware upgrade
9) by this firmware upgrade your device will be completely wiped and reinstalled
Good luck!
Bernard
Click to expand...
Click to collapse
So this is what the content of the official APK file look like when you extract it with 7-Zip:
The instructions above said to rename the 70,6MB file "data" to "update.zip" and place it on the SD card, and "randomly" a notification should appear, mentionning "Firmware upgrade found". No luck, no notification.
But still... That "data" file has the structure of an official update.zip file... I'm almost certainly sure that what the APK file does, it just rename the huge "data" file as "update.zip", and then just reboot into Stock Recovery and flash, huh?
So it's technically a trick, renaming the "data" file as "update.zip", but it still remains from the official firmware, yeah? How weird. I still don't understand that "Signature verification failed", then...
Doesn't make any sense.
As far as the bootloader is concerned, i don't if it is locked. You have to boot to bootloader mode (if any??). If you want to unlock it and the vendor deosn't provides any tools then, yes, you have to hack it. This is done by reverse enginnering and as you said you have to find an exploit. Or maybe you can flashed an "unlocked" bootloader if the partition isn't signed by the vendor.
Click to expand...
Click to collapse
There are no public infos on that bootloader anywhere. I had to e-mail the vendor, Creative, which told me the bootloader was locked (Is that even true? Ha, I guess so, but no way for me to verify the statement).
If only I had Fastboot, I could have tried "fastboot oem-unlock" on day one, but it doesn't appear to have Fastboot at all, or it's not accessible (To my knowledge, it could be hidden, but I really have no idea. Just thinking of my LG P500, which you can't access Fastboot the normal way, unless you soft-brick, or you manually enable it with a special software. Done that, on LG P500).
The commmand adb reboot bootloader doesn't work, neither reboot bootloader, with SU rights from Terminal Emulator. It just reboot the system normally. Also tried "adb reboot-bootloader", no luck. Hey, even "adb reboot recovery" just reboot the system normally, without accessing Recovery 3e.
In fact, I believe it just ignores the other arguments somehow. I can type rubbish like this, in Terminal Emulator:
Code:
$ su
# reboot jriogjrog
...Instead of popping an error, it still reboot normally. Huh.
I also have a USB-jig, but I always thought it was intended for Samsung only, and besides, my Jig is a microUSB, while the ZEN Touch 2 has miniUSB, just doens't fit in the port.
There seems to be nothing, tried every hardware key-combos out there, no way to reach bootloader-level, no Download Mode, no Emergency Mode, no Fastboot... Only hardware key-combo is "Home+Power", which access Recovery Mode, that's all.
This is the partition table. From what I see, I strongly believe /Recovery and /Boot are united as one single partition. Obviously, since it's an entertainment device but not a phone, it has no modem/baseband partition. Pretty simple. Appears to use non-standard NAND partitioning (Wow). With an MS-DOS partition table (GPT was new in 2010, isn't it?), so the Block 3 is just an extended partition.
BUT, from what I see, Block 4 start at 158MB, so there would be 158MB of unused space at the start of the NAND ???? Or that part of the bootloader in any way (158MB for the bootloader, no way?) ? Or maybe Creative are just dumb XD Or this could be some sort of Master-Boot-Record just like on computers like GNU-GRUB, but I've never heard of that on Android, we refer to simply a /Boot partition.. Which I still believe /Boot and /Recovery partitions are combined.
But if you don't have fastboot you can f;ash anything. Jtag is solution but it is difficult and you need expensive equipment.
Click to expand...
Click to collapse
I've heard of JTAG, the process of connecting the motherboard to a JTAG box, and reflashing the bootloader that way - Didn't knew this could be used to flash the whole system. Thought you would flash just the Bootloader and restore the rest with Odin, for instance.
A bit off-topic, but to use JTAG, do you have to have a special bootloader file, or can you flash the bootloader using, for example, the u-boot-no-padding.bin file we have here?
Do the device (especially older devices like this one) requires special connections, or connectors, so if the connectors don't exist, no way to JTAG? Oh well, that's not the main topic anyway, just curious, you really seem to know your stuff.
Thank you very much
This is a thread for the rooting and install of TWRP for the Uefone Power 3
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
TWRP 3.2.1-0: https://drive.google.com/file/d/1cLqcDrun5f6h1BHjUFfXDdlhwEWwM-49/view?usp=sharing
SuperSU: https://drive.google.com/file/d/1sZwahrodGJmYWzaIohxEETeIAabCOPfb/view?usp=sharing
Steps to install TWRP and SuperSU
Copy the above SuperSU to your SDCard.
First of all, you will be required to unlock your bootloader.
There is an option for this under Developer Options in the settings menu. Activate this.
Also activate USB Debugging. This makes this a whole lot easier.
Now, open a terminal, if on Linux, or command prompt if on windows, and enter the following:
Code:
adb reboot bootloader
Code:
fasboot oem unlock
Follow the onscreen instructions to unloack your bootloader. THIS WILL WIPE YOUR DEVICE!!!
Once this is complete, it will go back to the fastboot screen.
Now, from within your terminal/command prompt, navigate to the folder where you have downloaded the above recovery.img to.
Enter the following command once there:
Code:
fastboot flash recovery recovery.img
This will flash TWRP to your device, overwriting the stock recovery.
Once this is complete, there will be a screen telling you how long it took etc. Now you need to hold down your volume up button, and power button. Keep holding these untill you reach the menu for recovery, fastboot or normal mode.
Select Recovery.
This will boot into TWRP for the first time. when you get there, you will be prompted with a screen asking for a password. Cancel this.
WHAT EVER YOU DO, DO NOT FORMAT DATA LIKE IT ASKS YOU!"" YOU WILL LOSE TWRP!!!
Your then presented with the main TWRP screen, go ahead and tap on Install. Next, hit Select Storage, and select Storage 1. This is your SDCard.
Now flash SuperSU.
When this is installed, reboot to your main system, and update the SuperSu binary.
Now proceed to reboot back to recovery, how ever you wish.
Once in recovery, go into Wipe, and hit Format Data, this will wipe your phone again, but youve just done this anyway so it doesnt matter
Now flash SuperSU again, just to be safe, the same way as above.
Reboot to your system, and your done!
You will have to go through the setup of the whole android system again, but its worth it your now rooted and have TWRP to install the Custom ROMs that will be coming shortly
Have Fun!
Reserved
wow, that was quick thank you
will try it now and update as soon as it's done!
alright, so i tried to flash super su, but i never get to access the storage partitions (i think they are not mounted).
so i tried to factory reset / wipe the phone to get rid of the encryption, but i still cant select storage 1 from the menu.
here some more detail:
- i have already had the bootloader unlocked
{
"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 i come to this screen when twrp starts, and select "swipe to allow modifications"
- then i press install and want to select "storage 1", this however doesnt work. (due to encryption?)
- i tried to mount it, but cant even mark it active. just gets gray for half a second and then nothing
- tried to do a wipe via twrp as well, with no success
any ideas?
tbst1337 said:
alright, so i tried to flash super su, but i never get to access the storage partitions (i think they are not mounted).
so i tried to factory reset / wipe the phone to get rid of the encryption, but i still cant select storage 1 from the menu.
here some more detail:
- i have already had the bootloader unlocked
- then i come to this screen when twrp starts, and select "swipe to allow modifications"
- then i press install and want to select "storage 1", this however doesnt work. (due to encryption?)
- i tried to mount it, but cant even mark it active. just gets gray for half a second and then nothing
- tried to do a wipe via twrp as well, with no success
any ideas?
Click to expand...
Click to collapse
Your third screenshot - what's the last option, under Microsd?
Also, when going through install, can u see "external SD"?
ukhellfire666 said:
Your third screenshot - what's the last option, under Microsd?
Also, when going through install, can u see "external SD"?
Click to expand...
Click to collapse
the last one is USB OTG, also showing 0MB - i actually tried flashing supersu through the usb as well, with no luck
i can see external_sd but there dont seem do be ANY contents
do you think it is the encryption? because everything shows 0MB in brackets
EDIT:
i just thought what the hell i try again to flash it via usb. havent changed anything but suddenly SUCCESS
appreciate your time thanks
tbst1337 said:
the last one is USB OTG, also showing 0MB - i actually tried flashing supersu through the usb as well, with no luck
i can see external_sd but there dont seem do be ANY contents
do you think it is the encryption? because everything shows 0MB in brackets
EDIT:
i just thought what the hell i try again to flash it via usb. havent changed anything but suddenly SUCCESS
appreciate your time thanks
Click to expand...
Click to collapse
So what did you do differently? If you can explain a bit more, I'll change/add it to the guide. Maybe as a second option or something...?
ukhellfire666 said:
So what did you do differently? If you can explain a bit more, I'll change/add it to the guide. Maybe as a second option or something...?
Click to expand...
Click to collapse
i just booted again into twrp and suddenly my 4gb usb was showing up as the only thing not 0mb, so the usb otg partition was mounted. from there on i just pressed install and located the zip file on the usb drive. had some errors. below some pics i took with my old phone:
tbst1337 said:
i just booted again into twrp and suddenly my 4gb usb was showing up as the only thing not 0mb, so the usb otg partition was mounted. from there on i just pressed install and located the zip file on the usb drive. had some errors. below some pics i took with my old phone:
Click to expand...
Click to collapse
Ahhh brilliant! I don't suppose u found that he sdcard was mounted too did you?
Have the errors gone now your rooted? The rest of the guide should still count...?
ukhellfire666 said:
Ahhh brilliant! I don't suppose u found that he sdcard was mounted too did you?
Have the errors gone now your rooted? The rest of the guide should still count...?
Click to expand...
Click to collapse
yes i am indeed rooted!
everything else, including internal storage was 0mb as well. usb otg was literally the only one.
i have not gone back into recovery since, but rebooted several times and also used root apps (adaway). everything seems to work great and the rest of the guide still counts!
in total, everything seems stable until now :good: my goal is to not touch twrp anymore until android 8.1 will be released
tbst1337 said:
yes i am indeed rooted!
everything else, including internal storage was 0mb as well. usb otg was literally the only one.
i have not gone back into recovery since, but rebooted several times and also used root apps (adaway). everything seems to work great and the rest of the guide still counts!
in total, everything seems stable until now :good: my goal is to not touch twrp anymore until android 8.1 will be released
Click to expand...
Click to collapse
The official 8.1 update with overwrite TWRP.
I am now working on a cm14.1 build. As im having to use a prebuikt kernel, this is as far as I can go.
As soon as I have a beta ROM I'll upload.
Don't suppose you could boot to recovery and just double check that everything is as it should be? Put my mind at ease, make sure it works for you, as it does for me...
ukhellfire666 said:
The official 8.1 update with overwrite TWRP.
I am now working on a cm14.1 build. As im having to use a prebuikt kernel, this is as far as I can go.
As soon as I have a beta ROM I'll upload.
Don't suppose you could boot to recovery and just double check that everything is as it should be? Put my mind at ease, make sure it works for you, as it does for me...
Click to expand...
Click to collapse
sure man, maybe joining me on discord would make this process faster https://discord.gg/jPZqn4
Hi.
Thank you for twrp.
I am trying to use SuperSu with SuHide, i wipe data with this twrp to be able to install supersu in BINDSBIN mode to /data but data partition stay unencrypted to be mountable with thw twrp.
How to encrypt it back with own known password keeping supersu and suhide working?
TWRP has no option to reformat with password, no way to get origin password for stock recovery formated partition.
Any idea?
MioCZ said:
Hi.
Thank you for twrp.
I am trying to use SuperSu with SuHide, if i wipe data with this twrp to be able to install in BINDSBIN mode to /data but data partition stay unencrypted.
How to encrypt it back with keep supersu and suhide working?
TWRP has no option to reformat with password, no way to get origin password for stock recovery formated partition.
Any idea?
Click to expand...
Click to collapse
No idea I'm afraid. Sorry.
I used encryption in system Setup, i works, but with unknown password stored somewhere in nvdata partition. I am worry about loose root after OTA update and without pasword for twrp no way to get again to data partition.
I'm thinking of buying this phone. It's great to see that root already seems to work and that there might be a CM/LineageOS Rom soon. Root and custom recovery is crucial so one reason less to not buy it.
Are you guys happy with it in general? Does the dual camera work with bokeh and shoot good photos with low lag required to capture playing kids? Good value?
I can not install Snap Chat
Thank you ukhellfire666
The recovery was successfully installed
My question:
is there any idea to fully remove superSu to install snapchat
A full system backup has been taken.
DaF1974 said:
I'm thinking of buying this phone. It's great to see that root already seems to work and that there might be a CM/LineageOS Rom soon. Root and custom recovery is crucial so one reason less to not buy it.
Are you guys happy with it in general? Does the dual camera work with bokeh and shoot good photos with low lag required to capture playing kids? Good value?
Click to expand...
Click to collapse
good day to you.
in general i am happy with it, but the camera really blows. it is - without a doubt - the worst camera i had since my LG VX-5200. iphone 6s and galaxy s6 have way better cameras.
i am really frustrated, because they advertised the 4 cameras ..." " heavily, but they really suck. maybe it's just with the stock app and another app would make it better (but somehow i doubt that)
tomorrow i will go on holiday and was stoked that the phone arrived before, so i could take it with me to take pictures etc. seems like i will need to get the old digital camera out....
alshyib said:
Thank you ukhellfire666
The recovery was successfully installed
My question:
is there any idea to fully remove superSu to install snapchat
A full system backup has been taken.
Click to expand...
Click to collapse
Is possible to flash un-supersu package. Is somewhere in SuperSu topic. Or you can flash clean ROM / your backups (boot.img, recoovery.img, system.img).
Because this i have used supersu in BINDSBIN mode and suhide. So i have hiden su, locked bootloader, working OTA and all root sensitive apps.
bootloop
Hello, I followed the instructions but my phone bootloop on twrp, it does not start the system can you help me please?
---------- Post added at 02:23 AM ---------- Previous post was at 02:21 AM ----------
Hello, I followed the instructions but my phone bootloop on twrp, it does not start the system can you help me please?