Database Develop

[Q] CM7 stuck in booting

Running 2.3.3, build number is CL 49208, using a Mac. Unlocked bootloader with fastboot. Used recovery-RA-passion-v2.2.1. Put the su-2.3.6.1 on my phone. Finally got it to reboot in recovery. Installed CM7.0.3. Oh, and I bought this phone in China (it's legit). Also, I used info from lots of sources before I finally found a recent post here that suggested the su zip file. One of those things I put in my sdcard is Radio_20100203_2_Signed_PASSION.img. Don't know if that helps. I couldn't find a more updated radio image.
The plan is to install CM7 so I can run openvpn.
It stops and cycles through the CM7 load screen -- turquoise android on a skateboard with an arrow circling around. Goes no further.
What did I miss? How do I fix it? Thanks.

Sounds like your in a bootloop.
Did you flash GAPPS also?
Here's more infos for radio, ect...
http://forum.xda-developers.com/showthread.php?t=744605

Has happened to me before. I removed the SD card and scanned it for errors on my PC. Worked after that. HTH.
Sent from my Nexus One using XDA App

Uhh...I can't put a microsd card in my computer -- I don't think.
Would you recommend updating the radio image? I'm thinking the 5.12.00.08, since my phone is in fact Korean. Do I still need the GAPPS image? Can I flash that image into my phone, or do I need to put it on the root of the sdcard?

cat3rpill3r said:
Uhh...I can't put a microsd card in my computer -- I don't think.
Would you recommend updating the radio image? I'm thinking the 5.12.00.08, since my phone is in fact Korean. Do I still need the GAPPS image? Can I flash that image into my phone, or do I need to put it on the root of the sdcard?
Click to expand...
Click to collapse
They make an adapter for micro sd card t ofit a USB port.
You can try new radio but If it's bootlooping I think your problem is elsewhere.
Did you check MD5SUM of the ROM before flashing?

Fortunately, my neighbor has a plethora of microsd adapters.
I did not check the sum. I read a few suggestions about doing that, but I couldn't figure out how, so I just trusted that what I had was fine. Lesson learned.
Let me get this straight: I need to put the GAPPS image on the sdcard AND flash the GAPPS image from fastboot? If I do update the radio image, do I need to reinstall CM7?

Put cm7 rom and gapps on sd card,
boot into recovery and flash rom then gapps, reboot.
Its highly recommends you do radio via fastboot.
To check md5sum, you can use one of the many free app from market.

Ok, ran checksum in fastboot. Not really sure what I'm looking for, so I'll just post what happened. In every case except gapps and su, the numbers returned were the same on the sdcard as in the tools file on my mac. Gapps and su are only on the sdcard.
For the CM7 zip, it returned: MD5(pathtofile)= 98d06d6a58c7de87d40269bfe0ae0e7b
For the RA img: 3def709ab1c9e051a92a1c8b1504a36a
For the Radio img: 310d85c4998163818f7dcdef730c2a12
For the gapps zip: 2f6a93654d1cfe191ff709b360ad60fc
For the su zip: b23147cb55eba3ae32a996a913fa54ea
I'm too new to the forum to post the link where I'm getting my instructions.
The CM7 version is update-cm-7.0.3-N1-signed, the RA is recovery-RA-passion-v2.2.1, the radio img is Radio_20100203_2_Signed_PASSION (the updated radio link you posted had removed the radio img because of some sort of violation), and gapps zip is gapps-passion-ERE36B-2-signed.
Still having the bootloop problem. I tried to find the most updated versions of everything I could. Is there a compatibility issue somewhere?

Another thought:
Do I need to flash the su zip from my sdcard in recovery? I don't know what that will do, so I haven't tried it yet.
There are a couple of files that Amon-RA suggests I delete in order to prevent calling the stock recovery:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
Any idea how I can check for and delete these using fastboot via mac terminal?

You can't delete them from fastboot. Use fastboot to boot off the new recovery and delete them in there through adb.
Code:
fastboot boot recovery "c:\location\to\recovery.img"

Can you be more specific? I use fastboot to flash the recovery image, and when I'm in recovery on the phone, I use adb from my computer? Or I can access a command line in the phone?

Well, you use fastboot to flash the recovery. Then you use the command I posted below so you can boot directly into that recovery. Once in there, you use adb on the computer to go into the phone, mount the system partition (which can be done under the mounts and storage menu in recovery) and then find those files and remove them.
But you really only need to delete those files if you want to stay running stock Android. If you have a custom recovery on the phone, that is all you need to install CM, and CM doesn't contain the files that revert the recovery back to stock.

Just got it to work. It was, in fact, a compatibility issue. The gapps zip was for a different version. I found a different zip (for Gingerbread) at: http://goo-inside.me/gapps. If you have Gingerbread, choose a zip with gb in the name.

[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!

Credits:
birbeck for the usual random java guidance, slushpupie for his previous java guidance, dodgejcr for extreme amounts of testing, and one_love_420 and shift for some great graphics!
testers: JT-, couga6442, happytweak and many others I might have forgot in the furry of three days I built the initial app from scratch!
HTC Vivid Testers: PirateGhost and IanWizard - thank you!!
Thanks to SDX
Device must be "unlocked"
HTC Unlock:
If you have a device which has successfully completed the HTC unlock method, this application will work to flash kernels and assist in flashing the kernels for ROMs!
Please see the guides at the bottom of this post!
Background:
flash_image (bmlwrite) is an extremely useful utility for flashing custom kernels, boot logos and recoveries. This binary has made it possible to easily flash all these items and is used almost everywhere behind the scenes (i.e. in custom recoveries, packaged into kernel /sbin, etc).
Description:
This android application, FlashImageGUI, is basically a GUI interface for the linux binary, flash_image provided by google in AOSP for loading custom kernels and recovery images onto the phone.
This app allows the flashing of kernels and custom recovery images in normal android mode!
Current Device Support:
Full Kernel, Logo and Recovery flashing: Samsung Moment, Transform, Intercept and Acclaim - the s3c6410 series of devices
Full Kernel (Anykernel and boot.img) Flashing and Recovery (zip file or image) flashing: HTC Vivid/Holiday, HTC EVO 3D CDMA and GSM, HTC EVO, HTC EVO Shift, Nexus S/Nexus S 4G & LG Optimus
Full Kernel (zImage) Flashing: Samsung Epic
Check application version for updates
Future Support:
Will continue to test kernels as they are released to ensure compatibility!
Install Directions:
Install process is the same as any other .apk. Download to computer and adb push or mount sdcard on computer and copy over or download directly to the phone. Use any file manager, adb, connectbot/terminal emulator to install.
My preferred method, maybe a bit technical: ./adb install c:\downloads\FlashImageGUI.apk
Download Locations
Market (99 cents!): Flash Image GUI
Release version (free from my personal hosting): Flash Image GUI
Contact:
Any questions, comments, concerns, or issues, please post in this thread, PM, tweet, IRC or send me an email! Thanks for all the help and support!
Screenshots:
{
"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"
}
Feedback:
Please post any helpful feedback. I'm always looking to improve the application!
HTC Unlock - User Guides for Flash Image GUI!!
HTC Unlock - Users Guide for ROMs with a Kernel (boot.img file):
1) Unlock using HTC method
2) Load this application, Flash Image GUI, onto the device, either through the Market or the link provided in this OP.
3) Download ROM .zip file to the sdcard on the device.
4) Open up Flash Image GUI, select Browse and select the ROM .zip file, downloaded to /sdcard in the previous step.
5) Flash Image GUI will provide a warning, reminding that the ROM .zip file will *need* to be flashed in the custom recovery afterward.
6) Flash Image GUI will index the full ROM .zip file searching for the kernel and kernel modules. Once located, the Flash Image button should be enabled.
7) Select the Flash Image button and Flash Image GUI will load the kernel and kernel modules from inside the ROM zip file.
8) Once completed, turn off the device. (Assuming you've already loaded a custom recovery)
9) Hold volume down + power to boot into the bootloader. Select recovery.
9) Inside the custom recovery, load/flash the ROM zip file.
10) Reboot to normal Android mode and all should work including Wifi!
HTC Unlock -Users Guide for flashing ONLY a Kernel (zip file):
1) Make sure the selected Kernel is compatible with the currently loaded ROM. If not, this will result in a lot of frustration!!! See troubleshooting steps below.
2) Download kernel zip file to /sdcard.
3) Open Flash Image GUI, browse and select kernel zip file, downloaded/loaded to sdcard in previous step.
3) Flash Image GUI will validate the kernel zip file is contains the minimum required files
4) Select the Flash Image button and Flash Image GUI will load the kernel and the kernel modules from the source kernel zip file.
5) Reboot
Troubleshooting after Rebooting:
First step, when experiencing issues flashing is to RE FLASH the files again. Many times, re flashing again will clear up any issues. If not, see the issues/solutions below.
Issue #1: If the device hangs or reboots while on the splash screen, the kernel (or packaged ramdisk in the kernel) is NOT compatible with your device!!!
Solution for #1: Have to boot into fastboot and load the custom recovery to flash a known good kernel or restore a previously known good nandroid backup. Command: fastboot boot c:\downloads\cwm-recovery.img
Issue #2: If the device hangs or reboots while on the boot animation, the ROM is likely NOT compatible with the kernel!!!
Solution for #2: Have to boot into fastboot and load the custom recovery to flash a known good ROM/kernel combination either from a zip file or restore from a nandroid backup.

Very cool, this will take away a lot of the headaches in the superguide thread lol.

Pleasure working with you again joeykrim and with pirateghost. Glad you got this phone supported with the quickness. Great work!

App worked flawlessly for me. I love that we're simplifying this process.

okay so im coming from the samsung captivate, so Im new to the htc. looking at the op, I still have to go to the htc site and unlock my phone first before I can do any of the other steps in the post right?

djfrost40 said:
okay so im coming from the samsung captivate, so Im new to the htc. looking at the op, I still have to go to the htc site and unlock my phone first before I can do any of the other steps in the post right?
Click to expand...
Click to collapse
Yes, good point. I added a note to the OP for that.
Unfortunately, HTC is not as simple as Samsung when it comes to allowing customization. There are other upsides though and with everything in life, it is a trade off! Welcome!

I unlocked my brand new AT&T Vivid today. Followed the superguide and rooted the phone, put on CWM 5.5.0.4.. Now I cannot figure out how to flash that boot image. I know I am suppose to extract the boot.img out of the zip, tried flashing it in HBoot, but didn't see it, This tool found it but warned me not to flash it. Is there something else that goes with the boot.img? want to flash Wild Childs rom

dudeluv said:
I unlocked my brand new AT&T Vivid today. Followed the superguide and rooted the phone, put on CWM 5.5.0.4.. Now I cannot figure out how to flash that boot image. I know I am suppose to extract the boot.img out of the zip, tried flashing it in HBoot, but didn't see it, This tool found it but warned me not to flash it. Is there something else that goes with the boot.img? want to flash Wild Childs rom
Click to expand...
Click to collapse
remember how you unlocked the phone?
exactly like that, only you need the boot.img and a slightly different command
fastboot flash boot boot.img
if you dont have fastboot in your environment path, then you need to be IN the same folder as fastboot.exe. the path to boot.img has to be exact, so if boot.img is NOT in the same folder as fastboot.exe you need to specify its path....
fastboot flash boot c:\users\username\desktop\boot.img

Pirateghost said:
remember how you unlocked the phone?
exactly like that, only you need the boot.img and a slightly different command
fastboot flash boot boot.img
if you dont have fastboot in your environment path, then you need to be IN the same folder as fastboot.exe. the path to boot.img has to be exact, so if boot.img is NOT in the same folder as fastboot.exe you need to specify its path....
fastboot flash boot c:\users\username\desktop\boot.img
Click to expand...
Click to collapse
Oh, okay, so put the Boot.img with the fastboot.exe in the same folder, run cmd with the with the phone in Bootloader and direct it to where the folder is located at on your PC.run this command if the folder is on your desktop fastboot flash boot c:\users\username\desktop\boot.img
I got it, Thanks.

dudeluv said:
Oh, okay, so put the Boot.img with the fastboot.exe in the same folder, run cmd with the with the phone in Bootloader and direct it to where the folder is located at on your PC.run this command if the folder is on your desktop fastboot flash boot c:\users\username\desktop\boot.img
I got it, Thanks.
Click to expand...
Click to collapse
if you have boot.img in the same folder as fastboot.exe, then no, just open a command prompt where fastboot.exe is, and run the command
fastboot flash boot boot.img

Pirateghost said:
if you have boot.img in the same folder as fastboot.exe, then no, just open a command prompt where fastboot.exe is, and run the command
fastboot flash boot boot.img
Click to expand...
Click to collapse
Oh okay, that sounds easier

dudeluv said:
Now I cannot figure out how to flash that boot image. I know I am suppose to extract the boot.img out of the zip, tried flashing it in HBoot, but didn't see it, This tool found it but warned me not to flash it.
Click to expand...
Click to collapse
Since we are in the Flash Image GUI thread, I feel inclined to answer the question regarding the application, Flash Image GUI.
There are a handful of warnings in the application because the HTC EVO 3D released in August of 2011 had this same HTC unlock method and I've been assisting people now for 6 months. There a handful of pitfalls which confuse many users and result in errors on their device. If you carefully read the warnings and follow the directions, you will prevent the common pitfalls and known issues.
1) This tool will warn you, but the warning doesn't say to NOT flash, it only warns you that you will be missing kernel modules if you ONLY flash the boot.img.
2) If you're wanting to load a ROM, as mentioned, select the whole ROM .zip file from Flash Image GUI. Flash Image GUI will handle all the logistics by scanning the file, locating the modules and kernel, and loading both of this. Make sure, after flashing the ROM .zip file in Flash Image GUI, the same ROM .zip file is flashed from recovery mode. Recovery mode will install the "system" portion of the ROM .zip while Flash Image GUI installs the "kernel" portion of the ROM .zip. If both portions are not loaded, many times the device will not boot.
3) When using Flash Image GUI, you don't need to extract the boot.img. It is better to select the whole kernel .zip file. The reason why is whenever you flash a kernel, boot.img or zImage, you MUST flash the accompanying modules, including WiFi. If not, most of the time, Wifi will NOT work.
If you find a warning to be incomplete or misguiding, please post up at least a portion of the exact text you see. I'm more than happy to revisit and working on improving wording but is hard for me to understand mis communications w/o exact feedback!
Let me explain why there is the warning for only flashing the boot.img. The modules (WiFi, etc) must match the kernel as they are compiled/setup at the same time. If the kernel mismatches with the modules, then the modules will not work. This is the main reason why there are posts saying, "Help, my Wifi stopped working".
Hope that helps clarify any confusion! Appreciate the support!

joeykrim said:
Since we are in the Flash Image GUI thread, I feel inclined to answer the question regarding the application, Flash Image GUI.
There are a handful of warnings in the application because the HTC EVO 3D released in August of 2011 had this same HTC unlock method and I've been assisting people now for 6 months. There a handful of pitfalls which confuse many users and result in errors on their device. If you carefully read the warnings and follow the directions, you will prevent the common pitfalls and known issues.
1) This tool will warn you, but the warning doesn't say to NOT flash, it only warns you that you will be missing kernel modules if you ONLY flash the boot.img.
2) If you're wanting to load a ROM, as mentioned, select the whole ROM .zip file from Flash Image GUI. Flash Image GUI will handle all the logistics by scanning the file, locating the modules and kernel, and loading both of this. Make sure, after flashing the ROM .zip file in Flash Image GUI, the same ROM .zip file is flashed from recovery mode. Recovery mode will install the "system" portion of the ROM .zip while Flash Image GUI installs the "kernel" portion of the ROM .zip. If both portions are not loaded, many times the device will not boot.
3) When using Flash Image GUI, you don't need to extract the boot.img. It is better to select the whole kernel .zip file. The reason why is whenever you flash a kernel, boot.img or zImage, you MUST flash the accompanying modules, including WiFi. If not, most of the time, Wifi will NOT work.
If you find a warning to be incomplete or misguiding, please post up at least a portion of the exact text you see. I'm more than happy to revisit and working on improving wording but is hard for me to understand mis communications w/o exact feedback!
Let me explain why there is the warning for only flashing the boot.img. The modules (WiFi, etc) must match the kernel as they are compiled/setup at the same time. If the kernel mismatches with the modules, then the modules will not work. This is the main reason why there are posts saying, "Help, my Wifi stopped working".
Hope that helps clarify any confusion! Appreciate the support!
Click to expand...
Click to collapse
Thanks for the clarification. I flashed a kernel last night Pirates way.
I have Flash Image GUI on my ROM. Correct me if I am wrong, some roms do not have the boot.img included in the rom, they have it separate, From what I understand is I would just include the boot.img, taken out of the zip and drop it into the rom, Then browse to where the rom is on the sd card with Flash Image GUI and then flash the boot.img..... go into recovery then flash the rom,
My original question, If I have the Boot.img out of the zip, drag it onto the sd card, is it okay just to flash the Boot.img alone? then turn the phone off and go into recovery, flash the rom?
When I tried it this way, I got warnings. So I posted that question.

dudeluv said:
Thanks for the clarification. I flashed a kernel last night Pirates way.
I have Flash Image GUI on my ROM. Correct me if I am wrong, some roms do not have the boot.img included in the rom, they have it separate, From what I understand is I would just include the boot.img, taken out of the zip and drop it into the rom, Then browse to where the rom is on the sd card with Flash Image GUI and then flash the boot.img..... go into recovery then flash the rom,
My original question, If I have the Boot.img out of the zip, drag it onto the sd card, is it okay just to flash the Boot.img alone? then turn the phone off and go into recovery, flash the rom?
When I tried it this way, I got warnings. So I posted that question.
Click to expand...
Click to collapse
Yes to all of the above.
Flash Image GUI will flash basically all the combinations you can create. I've added warnings though to caution uses who aren't familar with the process as I prefer not to see the Flash Image GUI bricked my phone posts/emails/market comments.
Well historitcally, most ROMs if requiring a kernel with either include it or link to a flashable .zip of it.
With this whole HTC unlock issue and confusion, some ROM devs are providing their ROM required kernel separately as a boot.img file.
The warning you received when attempting to flash just the boot.img file was only to inform you that you must immediately flash the associated ROM .zip file from recovery mode or the device might not boot properly.
Thanks for requesting clarification and I'll revisit the wording to verify the clarity. Appreciate the support!

joeykrim said:
Yes to all of the above.
Click to expand...
Click to collapse
Cool, next ROM I flash I am going to try this.

where can i find a kernal for my stock velocity 4g? (says in bootloader that its a holiday)

WinterKnights said:
where can i find a kernal for my stock velocity 4g? (says in bootloader that its a holiday)
Click to expand...
Click to collapse
Majority of customized kernels will be found in the Development board.
If you're looking for the 100% stock kernel, the best source is to extract them from the stock RUU files. These are generally leaked and posted by a user named Football. His threads are also usually in the Development board.
Good luck and appreciate the support!

This is an embarrassingly rudimentary question.
I HTC-Unlocked my Vivid (running GB 2.3.4), and successfully installed FlashGUI. However, after launching it, it wants root before going any further. I would have thought that would be necessary, but the instructions on the OP make no mention of it. They just state HTC Unlock as a pre-req.
Given everyone else's success in using the app, it's painfully obvious that I'm missing something. Any pointers ?
-RKA

rasar42 said:
This is an embarrassingly rudimentary question.
I HTC-Unlocked my Vivid (running GB 2.3.4), and successfully installed FlashGUI. However, after launching it, it wants root before going any further. I would have thought that would be necessary, but the instructions on the OP make no mention of it. They just state HTC Unlock as a pre-req.
Given everyone else's success in using the app, it's painfully obvious that I'm missing something. Any pointers ?
-RKA
Click to expand...
Click to collapse
Wow, over 10k users and for some reason this was never pointed out as clearly as you've mentioned. You're definitely right as root access is not mentioned in the OP. In the Android Market, I have it at the top, but on the forum made the assumption people knew root access was required.
Due to Android's security architecture, root access is required before being Android grants write access to the kernel or recovery partition.
Quickest way, is probably to use fastboot to load a custom recovery and flash the superuser.zip file. This will install the Superuser application along with the su binary and setup the correct permissions.
Once root access is properly setup, everything should be good to go!
In summary, as security changes, the most consistent method after using HTC's official unlock will be to use fastboot to load a custom recovery and flash the superuser.zip file.
Hope that helps!

Will it work using on an Inspire 4G?

How to Install 4.2 images, keep root and all data

**Disclaimer** If you don't understand what follows, don't attempt this. I'm not responsible for you softbricking your device,
This is a quick guide for how to install the new android without losing anything. You'll need fastboot for this. Also, before doing this, be sure to download the supersu cwm update zip, and have it on your sdcard. Make sure you also already have a custom recovery installed (I did twrp, but i'm sure cwm will work just as well). I would also suggest having a backup done, through titanium backup and through recovery, just incase.
First, download the factory images for the n7 from google's website. Decompress them (if you're in windows, you'll need winrar or something similar.) After you decompress the archive, there'll be another one inside (image-nakasi-jop40c.zip), decompress this one as well. Under here, you'll see the .img files for all the partitions. For now, go up one directory. You'll also see here bootloader-grouper-4.13.img. Once you have all this, reboot into the bootloader.
Once you're in the bootloader, you can update the bootloader to the new version (this step isn't needed, but I did it anyways). Plug into your pc, and type fastboot devices. Make sure it's not blank. If it is, you have to update drivers. If you can see the device, open up a command prompt, and cd to the directory that has the bootloader-grouper file. Type the following:
fastboot flash bootloader-grouper-4.13.img
then, after it's done, type:
fastboot reboot-bootloader
Now, you'll be booted back into the bootloader, it'll say 4.13. On to the rom.
cd into the folder image-nakasi-jop40c (make sure you see the files system.img and boot.img before you continue. If you don't see them, the next steps will do nothing but erase your kernel and system parition.)
now, you see the image files. Type the following (still in the bootloader)
fastboot erase system
fastboot flash system system.img
wait until it completes, then type:
fastboot erase boot
fastboot flash boot boot.img
Once this is done, hit the volume up on the device until it shows recovery mode on the top. When it does, push the power key and you'll boot into your recovery (shouldn't be touched.) Inside here, flash the supersu cwm zip file, which'll flash the superuser binary, and supersu. Once this is done, do a factory reset (removing your data and cache.) Boot into the rom.
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
My first boot got stuck for some reason. if it happens to you, just hold the power button and hard reboot. (I did this on 2 devices, it only happened to one of them, so I figured I'd give you all warning.)
Links:
SuperSu binary: https://docs.google.com/open?id=0B7a8xHNJlpgTR0ZkR1pWZWR2VzA
Google Factory Images: https://developers.google.com/android/nexus/images

Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?

Thanks for this.. Apparently you found out too a clean 4.2 isn't rootable via typical methods.
That SuperSU package did the trick. I have to remember to keep a SuperSU binary on hand for these kinds of situations that SuperUser fails..

jefferson9 said:
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Click to expand...
Click to collapse
Yes. If you do it though cwm, you're not using any exploits, you're just inserting the superuser binary and supersu.apk into the proper places on the rom. On any nexus device, any rom, this will root it.

mstrk242 said:
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place.
Click to expand...
Click to collapse
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.

tehSmoogs said:
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
Click to expand...
Click to collapse
Exactly.
If everything goes right we should have an AOSP prerooted build in about *looks at watch* 20 minutes.... Unless there is a compile error or SU error. *laff*
Back to watching the scrolling terminal window

Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!

kwhee07 said:
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
Click to expand...
Click to collapse
I did this all on linux, just kind of adapted the guide for windows. I figured all the linux users would understand how to do it on their own. Glad to know it's the same for mac as well.

OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/

rootbrain said:
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
Click to expand...
Click to collapse
Settings - about tablet - build number
push it a few times and it will enable dev options

You have .bat file in the package.

Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...gned-nakasi-JOP40C-from-JZO54K.094f6629.zipia
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.

Here is my method:
1. Download official 4.1.2 from http://forum.xda-developers.com/showthread.php?t=1929270 and 4.2 OTA image from http://forum.xda-developers.com/showthread.php?t=1989188
2. Boot into CWM (i have CWM touch installed)
3. Clear data and install 4.1.2, don't forget to turn on root in the installer
4. reboot check that root is fully working
5. reboot into recovery install 4.2
6. before reboot CWM will ask to disable recovery flash and protect root. Ansver yes to both questions

I'm confused, it says if you are already on a custom rom, just flash as usual.
What makes this different?

I was on stock ROM rooted with some system modifications, and this wwadd the only way I could get the update working...
Sent from my Nexus 7 using xda app-developers app

mstrk242 said:
For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
Click to expand...
Click to collapse
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.

Ill have to wait until a rooted rom is created, I have no comp.
Sent from my Nexus 7 using XDA Premium HD app

can I install image-nakasi-jop40c.zip directly without upgrading bootloader?

Zuk. said:
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Click to expand...
Click to collapse
Not advisable to move this folder - if it got moved to a new location by the o/s then there's probably a good reason why - maybe like 4.2 introducing multiple users
Each user appears to get their own "home" directory created in /mnt/shell/emulated/
Default user dir is "0"
Second user dir is "10"
Each contain the standard dir's from 4.1 and earlier.

Travelawyer said:
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Click to expand...
Click to collapse
You had two extra characters at the end of your link, but I fixed it above and it's good to go for others in the future. Just flashed it in TWRP, it didn't ask if I wanted to maintain root, hit reboot when it was complete and lost root, so it doesn't work for everyone - good news is that all my data remained intact without having to resort to advanced restoring my data from a backup....
When I tried the SuperSU binary root flash trick, I finally got root back. But don't think it's as easy to get to recovery! I had to obtain the TWRP Recovery one more time since it wiped it and put in place a recovery that did absolutely nothing but reboot the device after a few minutes, so you'll have to
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
to get TWRP back.... Hope that helped everyone!

[ROM][TWRP](Stock? PL1) Samsung Galaxy J3 Emerge SM-J327P

Hello J3 Pop users. I have here a "backup" of the PL1 firmware made using TWRP. This flash procedure may be necessary if one can not flash the Odin ROM because of any number of failures (there seems to be a common problem with this). I am not positive if this is stock, or pre-rooted.
If you're looking for an Odin file, check here https://forum.xda-developers.com/general/general/rom-pl1-samsung-galaxy-j3-emerge-sm-t3580396
First off, DISCLAIMER: This is not a factory approved flash method, and if you haven't done so already, may void your warranty, or brick your device. Use at your own risk.
Now, with that out of the way, you will need to install TWRP, if you haven't already. That can be obtained from this link:
https://forum.xda-developers.com/ga...overy-twrp-3-1-0-1-samsung-galaxy-j3-t3573607
Just follow the flash instructions, but you don't need to attempt to root it... that part might fail in this case anyways.
Download the file from this link. you will need to extract the folder inside to ".\TWRP\BACKUPS\{device serial}" on your SD card. If you don't see this folder, just create any kind of backup from inside TWRP, even just the "EFS" partition will create the folder you need.
With the files and SD card in place, select "restore" inside TWRP. Select the partitions to restore, and there are two partitions labeled with system, i would recommend restoring both. The "EFS" and "EFS2" partitions should never be restored unless you know beyond a shadow of a doubt that those partitions are corrupted (it rarely happens, even when a device is bricked).
https://drive.google.com/open?id=0BxL3I-2U6frBOFRaSG1UYXd3WWc

So is this flashable via TWRP recovery, or Odin?

Schmitin said:
So is this flashable via TWRP recovery, or Odin?
Click to expand...
Click to collapse
clearly it is flashable via twrp (the last link)

thepcwiz101 said:
clearly it is flashable via twrp (the last link)
Click to expand...
Click to collapse
so on TWRP when I go to flash the recovery nothing shows. is there anyway to fix that?
EDIT: I fixed it. I put it in the wrong folder.

Hey! I really need this file! please send me if you have a backup, I would really appreciate it!
@Greaper88 Please give me access

[OFFICIAL] Motorola Edge 5G Racer TWRP

The developers have a lot going on at the moment, i know many have been asking for it, now that it is Official, i think it's safe enough for Public Use. I'm sure the DEVs will post a "more Official" Thread in the right spot. I did not post under Recovery because that is for DEV Use ONLY.
Official TWRP img and Installer zip : https://twrp.me/motorola/motorolamotoedge.html
***Dont forget to flash copy-partitions.zip if you are flashing a Custom ROM. The main device trees now include this, meaning it comes with MOST, NOT ALL, Custom ROMs. YOU WILL NOT BREAK ANYTHING, if the Custom ROM you are flashing already includes this and you flash the copy-partitions.zip. Better to be safe then sorry. This is required anytime you fastboot flash back to STOCK Firmware.INSTALL "Copy Partitions Zip" FROM POST #2
Installation:
NOTE: Your bootloader MUST be UNLOCKED before booting or installing TWRP If you already have TWRP installed: Download the latest zip and install the zip using TWRP, or flash directly the image directly to recovery in fastboot. If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have the latest fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader menu. Connect the device to your PC. Open a command window and run the following command from the proper location:
Zip method: fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. Use ADB or MTP to push the zip onto your device:
adb push path/to/twrp.zip /sdcard
Go to install and browse to the zip and install the zip. The zip will install TWRP on recovery partition of both slots.
Image Method: fastboot flash recovery_ path/to/twrp.img

Moto_Fan said:
The developers have a lot going on at the moment, i know many have been asking for it, now that it is Official, i think it's safe enough for Public Use. I'm sure the DEVs will post a "more Official" Thread in the right spot. I did not post under Recovery because that is for DEV Use ONLY.
Official TWRP img and Installer zip : https://twrp.me/motorola/motorolamotoedge.html
***Dont forget to flash copy-partitions.zip if you are flashing a Custom ROM. The main device trees now include this, meaning it comes with MOST, NOT ALL, Custom ROMs. YOU WILL NOT BREAK ANYTHING, if the Custom ROM you are flashing already includes this and you flash the copy-partitions.zip. Better to be safe then sorry. This is required anytime you fastboot flash back to STOCK Firmware.INSTALL "Copy Partitions Zip" FROM POST #2
Installation:
NOTE: Your bootloader MUST be UNLOCKED before booting or installing TWRP If you already have TWRP installed: Download the latest zip and install the zip using TWRP, or flash directly the image directly to recovery in fastboot. If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have the latest fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader menu. Connect the device to your PC. Open a command window and run the following command from the proper location:
Zip method: fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. Use ADB or MTP to push the zip onto your device:
adb push path/to/twrp.zip /sdcard
Go to install and browse to the zip and install the zip. The zip will install TWRP on recovery partition of both slots.
Image Method: fastboot flash recovery_ path/to/twrp.img
Click to expand...
Click to collapse
Having a problem, even unlocking the bootloader. Unlock my device, doesn't show a blue button, and msg, says"it can't be unlocked" . In any case, I downloaded all the software that was on page, when I can figure this out.

reggjoo said:
Having a problem, even unlocking the bootloader. Unlock my device, doesn't show a blue button, and msg, says"it can't be unlocked" . In any case, I downloaded all the software that was on page, when I can figure this out.
Click to expand...
Click to collapse
If you can't go passed #1, don't go any further, but I can only recommend.